Hello everyone! I hope to find some help here.
First lets start off by saying I tried to fix the WIFI problem that happends when flashing CM11 - "Wifi Turning On..." stuck error.
To which none of the fixes worked for me.
- Factory restore
- Persist folder replacement with download from thread
- Skeevydude blck download
Now I have formated all my folders (probably a horrible idea), woops.
Now I cannot do a factory restore with RSD Lite, I get error: gpt_main* Phone Failure - Yes I am trying to restore back to 4.1.1 or 4.1.2 - Tried both, same error.
Does anyone know how I can get my Firmware folder back or add what is needed? This seems to be the cause of the problem.
Thanks
Tags-
@skeevydude
Is there anyway to restore my "Firmware" root folder and get "Wifi" working again. As above I already tried placing driver files into "Persist".
Also I am running Cynogenmod 11.
Related
Hello everyone i am new to rooting and flashing devices and kinda stuck with a problem. I have a Samsung Galaxy s with
Firmware 2.3.3 Gingerbread
with Build number DDjv9
I tried flashing the the rom using oden3 with CF-root....tar file and then installed superuser through recovery...At 1st the phone was stuck in a loop and it kept rebooting ..i tried another cf-root file and that fixed the looping and rebooting problem ...Now ths issue is it dosnt detect my sim card...and dosnt allow me to use wifi...i tried many other files ...tried factroy reset frm recovery and even tried to reset using the code...noting works the phone just resets and i can see superuser app in the menu...
Really wish i could get some help on how to get my simcard to work again and wifi..Or even get my phone back to stock rom.
Thanks in advance
Have you tried reflashing with another romhttp://forum.xda-developers.com/showthread.php?t=1136449)? Did you backup your efs folder (using for exemple nitrality), if you did, try restoring your efs folder.
Hi,
This is my first post so please if I'm in the wrong place or doing anything wrong please let me know.
My problem and yes I am the fool to blame! The other night I was playing with root explorer and decided it would be a "great" idea to delete all the folders on my Milestone A854, PDS DATA etc etc.
What harm could it do? I just reinstall a rom back on and all sorted...... Wrong! I reinstalled roms using mini mod and then sbf files with RDS lite both producing the same outcome. A phone that displays the "M" Motorola logo then turns off and tries again......repeatedly!
Any help would be GREATLY appreciated.
Hello,
I know for me, I did the same thing with my Motorola Droid. But the thing is I didn't know what files the Droid had when it was in factory mode. So I decided to flash back to the original, in my case Verizon, SBF file. Then I rebooted, and let my phone update itself to the latest version, then did the whole "rooting" process, with the same rom I've been using.
Hope that helps
~Jin
Thanks Jin,
My problem here is I don't know what it had in the first place? I've tried flashing stock UK SBF but that just puts you in the Motorola boot loop so no opportunity to update.
Any further help/suggestions would be greatly appreciated.
Dave
im sorry if i get it wrong, so u cant get to recovery mode or sort of? i deleted one of the folder on /data n /system before, but i managed to entered recovery mode. n did the rest via console.
Yes I have and can still get to open recovery.
What could I try and do from there? I've tried with updates through this method the same way you put on custom firmware ( put the rom file in the open recovery updates folder).
So what do I need to do via console?
Still stuck with this one have tried stock sbf and custom roms all same problem BOOTLOOP have tried taking battery out then factory reset still same. Don't understand what wenderis means by "do the rest via console" ? So if any one out there can get my brick back to life you will be loved forever.
Hi everyone. I have a problem I can't seem to resolve. I tried updating to the OTA jellybean update a couple weeks ago, it seemed to go ok. I then tried to go back to an earlier version of eclipse rom I was using. Now when I power on the phone I get AP Fastboot Flash Mode (S) (Flash Failure). I can select normal boot and it will go into my ICS Rom that I have loaded in slot 1 after going thru my safestrap recovery program. So the phone is not unusable, just very annoying to use. My question is, how can I get the fastboot flash mode flash failure warning to not show up every time I reboot the phone? I've tried loading the Stock JB Rom from verizon, Blur_Version.6.7.246.xt875.verizon.en.us with RSD Lite, but when I try to extract the files with RSD, I get the error "Please check input file. Either XML format is wrong or image files associated with it are missing." I just want to be able to get a stock rom back on my phone, without any errors when I boot it, I don't care if I have root, safestrap, or anything else, I just want a properly working phone. Any suggestions how to get rid of the boot flash failure warning? Thanks!!!! Richard
Update.... Looks like I really screwed it up now. Tried to rsd lite a JB rom, got about 1/2 way, to copying system image, then hung up. Now when I reboot, it won't even go into recovery or normal mode... Stoopid operator malfunction..... Any suggestions on which rom I can try to install via RSD Lite to help get it back going? It will still go into AP fastboot mode.
He's dead, Jim. Nothing is working, no rom will load, they either fail or hang up. Now both of my batteries are dead, and it won't even try to do anything. Any suggestions?? Guess I'm in the market for another phone. Maybe some of the gurus on here have some advice. Thx.
He's alive, Jim!!!!!
rlg999 said:
He's dead, Jim. Nothing is working, no rom will load, they either fail or hang up. Now both of my batteries are dead, and it won't even try to do anything. Any suggestions?? Guess I'm in the market for another phone. Maybe some of the gurus on here have some advice. Thx.
Click to expand...
Click to collapse
Thanks to some other posts on here, http://forum.xda-developers.com/showthread.php?t=2236980 I tried installing the system and preinstall img files manually thru moto fastboot. They seemed to hang up after a few minutes, but I tried to install the files anyway. Afterwards, I was able to get into recovery mode and do a system wipe and reinstall the JB rom that I had on my SD card. Now a couple hours later, I got the pageplus 4g issue fixed again, and just finished rooting it with the tutorial on XDA http://forum.xda-developers.com/showthread.php?t=2256439.
You guys are awesome! Thanks for all your hard work.
Hi all
My GT-N7000 phone, running (it seems to remember) official Android 4.1.2 some days ago suddenly reset, driving me into the configuration procedure like the first time I switched on.
The following day it reset again, and went into bootloop on Samsung screen. I tried the following:
wipe cache data - no result
reset to factory data - no result
flash via Odin the N7000XXLT9_N7000ITVLT3_ITV Kernel - no result
When I went into recovery mode before reflashing kernel, I got the "can't mount /efs" error. After reflashing kernel, I installed PhilZ recoverty with Aroma, and discovered that the EFS folder is here, but it is EMPTY, and in fact I can't mount it even in PhilZ.
Another strange thing is that all my custom data are still on the telephone, despite the factory reset I have done.
I have searched a lot, but I can't find a way to solve my problem so I am asking you to help me
Thanks in advance
Paolo
Corrupted /efs partition on GT-N7000 causing bootloop
PaoloUrsini said:
Hi all
My GT-N7000 phone, running (it seems to remember) official Android 4.1.2 some days ago suddenly reset, driving me into the configuration procedure like the first time I switched on.
The following day it reset again, and went into bootloop on Samsung screen. I tried the following:
wipe cache data - no result
reset to factory data - no result
flash via Odin the N7000XXLT9_N7000ITVLT3_ITV Kernel - no result
When I went into recovery mode before reflashing kernel, I got the "can't mount /efs" error. After reflashing kernel, I installed PhilZ recoverty with Aroma, and discovered that the EFS folder is here, but it is EMPTY, and in fact I can't mount it even in PhilZ.
Another strange thing is that all my custom data are still on the telephone, despite the factory reset I have done.
I have searched a lot, but I can't find a way to solve my problem so I am asking you to help me
Thanks in advance
Paolo
Click to expand...
Click to collapse
Any help?
The only things I found on internet are two tools that assert to rebuild your EFS nv_data.bin file (RIFF box and Zx3 box), but I don't want to spend money because the /EFS get corrupted by itself, without any attempt to flash or modding or whatever else.
I think that reflashing kernel will not solve my problem, because (I think) the information are hardware related, and not software related. If needed, I am able to manually change the file reflecting the IMEI and S/N on my cell box, but I need a generic file and some references about positions...
Please guys help me... even if you have only bad news
Thanks in advance
Paolo
Was you phone rooted with a custom recovery before the issue started? Check in the clockworkmod folder in internal storage for efs backups like efs.img...
nokiamodeln91 said:
Was you phone rooted with a custom recovery before the issue started? Check in the clockworkmod folder in internal storage for efs backups like efs.img...
Click to expand...
Click to collapse
nokiamodeln91, thank you for the reply.
Unfortunately not, my phone wasn't rooted before the issue, and, strange enough, I didn't do anything particular on the device other than calling and browsing...
Now I installed PhilZ and have a complete backup, perhaps it's later
PaoloUrsini said:
nokiamodeln91, thank you for the reply.
Unfortunately not, my phone wasn't rooted before the issue, and, strange enough, I didn't do anything particular on the device other than calling and browsing...
Now I installed PhilZ and have a complete backup, perhaps it's later
Click to expand...
Click to collapse
Hi, friend of mine ask for help yesterday with his N7000 and he has the same problem as yrs.
I rooted the phone to have a look at the efs folder and it was empty.
As the factorymode was in OFF, I thought of creating an imei folder with root explore, lo and behold as soon as i saved it it received an a sms message.
Iopen the folder and there were the nv.data folder there.
Baseband was restored but the imei was a generic one 00000049 with the serial number at 0000000 but the consolation was he is able to use the phone normally with all services from telco and even package data was working.
My friend was so happy that he was able to use the phone and was willing to live with it not wanting me to try any further.
So maybe you can try this to get the phine working and like my friend live with it haha.
One more thing if ut works for u save the efs folder and try n restore it.I dont have the chance to try as my friend dont want to bugger it agian.
Also if you swich off the phine u may have to do it again. Cheers
Edit: Phone was in bootloop too, I went to recovery and it cant mount efs.I did a wipe twice and it started up that was how i was able to access the efs folder after rooting it. Cheers
ndmuni said:
Hi, friend of mine ask for help yesterday with his N7000 and he has the same problem as yrs.
I rooted the phone to have a look at the efs folder and it was empty.
As the factorymode was in OFF, I thought of creating an imei folder with root explore, lo and behold as soon as i saved it it received an a sms message.
Iopen the folder and there were the nv.data folder there.
Baseband was restored but the imei was a generic one 00000049 with the serial number at 0000000 but the consolation was he is able to use the phone normally with all services from telco and even package data was working.
My friend was so happy that he was able to use the phone and was willing to live with it not wanting me to try any further.
So maybe you can try this to get the phine working and like my friend live with it haha.
One more thing if ut works for u save the efs folder and try n restore it.I dont have the chance to try as my friend dont want to bugger it agian.
Also if you swich off the phine u may have to do it again. Cheers
Edit: Phone was in bootloop too, I went to recovery and it cant mount efs.I did a wipe twice and it started up that was how i was able to access the efs folder after rooting it. Cheers
Click to expand...
Click to collapse
Thank you ndmuni,
I don't understand very well what you did; consider that my phone is in bootloop, so I am not able to read an eventyually SMS, but I can accesso to file system with Aroma tool in PhilZ recoverty tool. Have I to create a special folder under root in my N7000? With what name?
Thank you in advance
Paolo
Hey guys!
So, here's what happened, step by step
I was on a BlissPop 5.1.1, but I wanted to install xposed. I hadn't any truly funcional recovery, only the built-in CM recovery. So I was trying to install one.
I found and .img file of twrp, then I flashed it thru flashtool, as the guides told me. But than I got stuck on twrp and, as I didn't expected it, I didn't made a backup. In another place, I found a guy saying that it was an issue that happens when you lose the misc.img file, and you can skip the 'flashing the ROM all over again' step just by flashing this file.
Then I downloaded it and my device softbricked. And then I look to do the same stuff that we always do when the phone got softbricked: install the stock firmware all over again.
I know I did a lot of mistakes and complicated the whole thing, but here was when something that I didn't know how to fix appeared:
I put it on flash mode, green light, but it just can't flash the tft file. The device keeps connecting/disconnecting over and over and when it finally starts to flash, I got the message "error in the processHeader: 5 - access denied" and I can't find a solution anywhere, not anyone with the same issue, nothing.
Right now I'm installing the PC companion to check if it is a driver problem, but I need to hear from you guys some advice to fix this.
Thanks a lot