Related
Okay so let's start off by saying my cousin is an idiot. He tried pulling an April fool's joke on me (ill spare you the details) and ended up wiping my phone THROUGH THE STOCK METHOD (As in going to settings and resetting the phone...). And so, im left with a phone in bootloop... awesome. So I need some help reviving it. I have no freaking clue if I still have clockwork running on it (i think it is because the boot animation for the ROM i was running is still there and the unlock thing at the bottom when it first boots up is there). I was running AOKP beta 25 with lean kernel along with the lucid theme atop of AOKP. Can someone please help guide me on how to get my phone up and running?
azn android said:
Okay so let's start off by saying my cousin is an idiot. He tried pulling an April fool's joke on me (ill spare you the details) and ended up wiping my phone THROUGH THE STOCK METHOD (As in going to settings and resetting the phone...). And so, im left with a phone in bootloop... awesome. So I need some help reviving it. I have no freaking clue if I still have clockwork running on it (i think it is because the boot animation for the ROM i was running is still there and the unlock thing at the bottom when it first boots up is there). I was running AOKP beta 25 with lean kernel along with the lucid theme atop of AOKP. Can someone please help guide me on how to get my phone up and running?
Click to expand...
Click to collapse
You may have to flash the stock google factory image. If you hold down both volume buttons and the power button while the phone is off, you can get into fastboot mode (the screen with the opened up Android). Then you can use the gnex toolkit (you can get it from the development forums) to flash the stock google factory image.
Just boot into recovery. You'll then know if you have CWM. If you have CWM, just try a data/cache/dalvik wipe and reboot. If it still bootloops, do a full wipe and re-flash the ROM.
If you don't have CWM, you can flash it through fastboot and try the above.
Don't freak out. A bootloop is about the farthest from a brick you can be.
what exactly will that do..? Will I lose unlock/root? and sorry if you don't mind, could you point me to the tool?
Alright so even after wiping and reflashing the ROM, im still in a bootloop. I dont mind having to go back to 100% stock no unlock if that's what it takes but can anyone help me out?
OK the easiest way to sort this out for you but perhaps not the best way is go to http://code.google.com/android/nexus/images.html and download a factory rom and use a tool kit like mskips http://forum.xda-developers.com/showthread.php?t=1392310 to flash everything back to stock. This will wipe your entire phone so back up anything you wanted to keep but I promice your phone will work again.
I only say this isn't the best possible way as it would be best to learn about adb and fast boot as to know how to do all this manually but I don't have a good knowledge on adb but its something I'm meaning to do just don't have a great deal of time for. The tool kit will do everything for you simply by pressing keys and a few clicks and will install all the drivers you need. Good luck
Sent from my Galaxy Nexus using Tapatalk
Thank you! I was able to flash to the stock image and keep my unlock! Sadly, since my cousin wiped my phone, i lost everything anyways... but I have my essential things (pictures, contacts, and some apps) already backed up. Thank you for your help!
azn android said:
Thank you! I was able to flash to the stock image and keep my unlock! Sadly, since my cousin wiped my phone, i lost everything anyways... but I have my essential things (pictures, contacts, and some apps) already backed up. Thank you for your help!
Click to expand...
Click to collapse
Glad you figured it out. Flashing the Google Images doesn't relock the bootloader (unless you explicitly do so with the oem lock command). You can now start over and load a custom ROM.
Good I'm glad you fixed it, today your learned a little bit of how to get out of sticky situations. I'm glad to of helped
Edit
Now be sure to return the favour to your cousins phone
Sent from my Galaxy Nexus using Tapatalk
It appears my A100 decided that it wanted to nearly 100% brick itself last night.
I'm stuck with only recovery at the moment and it is reporting that /dev/block/mmcblk0p4 and /dev/block/mmcblk0p8 are not found. I've tried plugging it into usb while in recovery to see about using ADB shell to recover the partitions but I cannot seem to get the USB drivers to recognize the device.
Anyone have ideas on what I can do as a next step?
Thanks to pio_maski and linuxsociety for helping us all out. For those just joining the thread:
pio_masaki said:
For everyone having the missing partitions error in this thread, once it starts its done, it began when the first freeze occurred.
At this point you have 2 choices, neither is fun and both involve Acer.
1 send it now and get charged for repair, they'll know its modded.
2 try to trigger fail safe and just plug it in, turn it on and let it sit and try to boot into android. After a set amount of failed /system or /boot reads it'll go into fail safe mode. Sending it under warranty in this state will have it repaired at no code aside from shipping to Acer.
You'll know fail safe is happening when you turn it on, blue or orange light comes on but the screen is off and there is no vibration on power on.
Both ways:
Get onto the Acer site and start a chat with a rep, tell them what happened. They'll ask you to hard reset after verifying warranty is still in effect time wise. After it fails this, they'll give you the info on sending it in. For me it took 10 days to get it back from sending it out.
Edit: for anyone that can still boot but hangs up, recovery may still be possible but its a very small window.
Click to expand...
Click to collapse
linuxsociety said:
If you have the brick, then there isn't any options left except to send it in to Acer for repair. They won't say anything about your ROMS/Kernels, however you need to find out if the stock bootloader needs to be re-flashed, and this will pretty much lock them out of recovery and everything when you do. They'll just end up replacing the board in the tablet and sending it back. I'm not 100% sure if anyone has sent their tablet in to acer with the a200 bootloader still intact and received their repaired tablet without a hassle, really that's the main thing you may want to check into.
Click to expand...
Click to collapse
I had the same thing happen to me last night.
Curious to know if you all were using stock kernels or a custom one? if custom which one?
linuxsociety said:
Curious to know if you all were using stock kernels or a custom one? if custom which one?
Click to expand...
Click to collapse
I believe mine was a stock kernel. I was using an unlocked boot loader, clockwork recovery 5.5.0.4 (I believe) and CM9 from 2012/07/08. Unfortunately that is about all the information I can provide. I was unable to use adb with CWR so I couldn't pull up more information on the nature of the problem. I ended up sending it back to Acer for warranty and got it back not 24 hours ago.
kemonine96 said:
I believe mine was a stock kernel. I was using an unlocked boot loader, clockwork recovery 5.5.0.4 (I believe) and CM9 from 2012/07/08. Unfortunately that is about all the information I can provide. I was unable to use adb with CWR so I couldn't pull up more information on the nature of the problem. I ended up sending it back to Acer for warranty and got it back not 24 hours ago.
Click to expand...
Click to collapse
The reason I asked was because I have been working on custom kernels and recoveries for the A100 to help in preventing this from happening, so I just wonder if anyone has had the mmc brick bug to occur while using one of my kernels in combination with my twrp recovery that also has userland mmc brick bug prevention patches.
linuxsociety said:
The reason I asked was because I have been working on custom kernels and recoveries for the A100 to help in preventing this from happening, so I just wonder if anyone has had the mmc brick bug to occur while using one of my kernels in combination with my twrp recovery that also has userland mmc brick bug prevention patches.
Click to expand...
Click to collapse
What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...
I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.
kemonine96 said:
What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...
I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.
Click to expand...
Click to collapse
The exact cause is unknown, however we do know that parts of the information the GPT partition table contains is wiped. There is no exact cause that we are aware of yet.
I wonder why so many people choose to use CWR over twrp? It would make sense to use CWR on devices that don't have TWRP support, but this one does and has for a while. I've never figured that out as the interface is much more trickier and when I have used it in the past i just seem to easily accidentally do the wrong thing with it. I dunno I guess people get accustomed to using one product and just never switch to something else.
linuxsociety said:
The exact cause is unknown, however we do know that parts of the information the GPT partition table contains is wiped. There is no exact cause that we are aware of yet.
Click to expand...
Click to collapse
Do the more recent recoveries include a good way to re-write the GPT partition table via an adb shell? Seems like if you can re-write the GPT partition table you'd be able to recover the device from mostly dead. Also, does the bug affect data stored on the various partitions? If so, are there images of the various partitions floating around?
linuxsociety said:
I wonder why so many people choose to use CWR over twrp? It would make sense to use CWR on devices that don't have TWRP support, but this one does and has for a while. I've never figured that out as the interface is much more trickier and when I have used it in the past i just seem to easily accidentally do the wrong thing with it. I dunno I guess people get accustomed to using one product and just never switch to something else.
Click to expand...
Click to collapse
Speaking for myself, I find that I can mash the hardware keys more efficiently via muscle memory than touch about a touch screen. Probably my old graybeard keyboard ways shining through...
I considered moving over to TWRP but the last I looked the information was a little lean (~1-2 months ago now probably). I planned on looking closer at it once the JB port is further along for the A100. Figured I'd jump to TWRP when I jump over to JB. I am aware the CM9 versions for the A100 are a bit out of date and I'm working on a build to address that (running repo sync while I'm at work).
kemonine96 said:
What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...
I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.
Click to expand...
Click to collapse
At this point its an unknown trigger, however the research on it shows Samsung and kindle fire devices with the same emmc we have are prone to the same issue.
As it stands now Linux society has patched the issue for Samsung devices in his kernel for Android and his kernel for twrp, its about the best protection we have at this time. While I may not agree to the trigger with him, its still a step taken against it that may well prove to be what prevents future bricks. Better safe then sorry kind of thing and I would suggest his recovery and kernel for this reason. Plus his kernel has a lot of extra goodies to play with
It works with all existing roms from ICS to JB, stock or modified or CM.
Tapatalked from my Galaxy S II.
pio_masaki said:
At this point its an unknown trigger, however the research on it shows Samsung and kindle fire devices with the same emmc we have are prone to the same issue.
As it stands now Linux society has patched the issue for Samsung devices in his kernel for Android and his kernel for twrp, its about the best protection we have at this time. While I may not agree to the trigger with him, its still a step taken against it that may well prove to be what prevents future bricks. Better safe then sorry kind of thing and I would suggest his recovery and kernel for this reason. Plus his kernel has a lot of extra goodies to play with
It works with all existing roms from ICS to JB, stock or modified or CM.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
You just had to sweeten the deal.... I will definitely add this higher on my ToDo list than I planned. I really don't want to go through the hassles of another warranty.
If it helps right before my device's GPT table died, I saw a massive CPU spike that caused my device to get quite warm. 2 or 3 hard power-offs and power cycles later my device was going out for warranty. After each boot before it went dead the CPU spike problem was still present and the device wouldn't even unlock from the lockscreen.
kemonine96 said:
You just had to sweeten the deal.... I will definitely add this higher on my ToDo list than I planned. I really don't want to go through the hassles of another warranty.
If it helps right before my device's GPT table died, I saw a massive CPU spike that caused my device to get quite warm. 2 or 3 hard power-offs and power cycles later my device was going out for warranty. After each boot before it went dead the CPU spike problem was still present and the device wouldn't even unlock from the lockscreen.
Click to expand...
Click to collapse
That is actually different from normal for emmc bricks, though makes sense too. If the file system is corrupt or missing then it would hog CPU time trying to find the data or fix the damage, if it even could.
Tapatalked from my Galaxy S II.
i think my a100 died just now for the same reason. i was running cm10 preview with 1.5 custom kernel for JB. Is there a way to restore the tablet? any help?
icomar said:
i think my a100 died just now for the same reason. i was running cm10 preview with 1.5 custom kernel for JB. Is there a way to restore the tablet? any help?
Click to expand...
Click to collapse
You need to give more details about what exactly your tablet is doing and what all was you doing when this happened? Can you still get to recovery? When you try to boot does it ever show boot animation? After turning the tablet on does the distorted Acer image still appear? Can you get adb connection at regular boot? Recovery adb? If you can get to recovery can you please give us your recovery.log file also? Thanks
Sent from my A100 using Tapatalk 2
linuxsociety said:
You need to give more details about what exactly your tablet is doing and what all was you doing when this happened? Can you still get to recovery? When you try to boot does it ever show boot animation? After turning the tablet on does the distorted Acer image still appear? Can you get adb connection at regular boot? Recovery adb? If you can get to recovery can you please give us your recovery.log file also? Thanks
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
you are right, so:
1) my tablet was charging, i unlocked it, it freezed. So i pressed the reset button under the tablet. Then it showed boot animation for ever.
2) i can access recovery (clockworkmod recovery) so i flashed cm9 instead of cm10, but the result is always the same, stuck on bootanimation after the distorted acer image that appears. Sometimes the tablet finishes boot, say "upgrading android" but never finishes.
I will try with adb later at home, and if you can tell me how to take the recovery.log i will provide it.
In this case what can i do?
icomar said:
you are right, so:
1) my tablet was charging, i unlocked it, it freezed. So i pressed the reset button under the tablet. Then it showed boot animation for ever.
2) i can access recovery (clockworkmod recovery) so i flashed cm9 instead of cm10, but the result is always the same, stuck on bootanimation after the distorted acer image that appears. Sometimes the tablet finishes boot, say "upgrading android" but never finishes.
I will try with adb later at home, and if you can tell me how to take the recovery.log i will provide it.
In this case what can i do?
Click to expand...
Click to collapse
That's not a brick. backup your apps with titanium backup, reboot wipe data, cache, dalvik, and system. Install your rom, gapps, kernel, etc.. Boot to android and install titanium backup, restore apps + data (only user apps not system!)
Sent from my A100 using Tapatalk 2
hello there, i did what you said (except for the titanium backup thing, i dont care about apps) that is the procedure to flash roms. after flashing the recovery freezed after saying "install completed" so i had to reboot manually the tablet from the power button.
still rom does not work (now the boot animation does not even show up).
PLUS if i try to wipe again the recovery says what you see in the attachment.
It is worse than before, am i right?
linuxsociety said:
That's not a brick. backup your apps with titanium backup, reboot wipe data, cache, dalvik, and system. Install your rom, gapps, kernel, etc.. Boot to android and install titanium backup, restore apps + data (only user apps not system!)
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
He's bricking. If he wipes cache then he will finish the job.
Edit: never mind I didn't see his update.
Tapatalked from my Galaxy S II.
pio_masaki said:
He's bricking. If he wipes cache then he will finish the job.
Edit: never mind I didn't see his update.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
now what? too late?
icomar said:
hello there, i did what you said (except for the titanium backup thing, i dont care about apps) that is the procedure to flash roms. after flashing the recovery freezed after saying "install completed" so i had to reboot manually the tablet from the power button.
still rom does not work (now the boot animation does not even show up).
PLUS if i try to wipe again the recovery says what you see in the attachment.
It is worse than before, am i right?
Click to expand...
Click to collapse
Well it definitely doesn't look good now. So the boot animation was appearing before you tried to do all the wipes and install from CWM? I just wanted to verify that this DID in fact take place while booted into recovery. You may want to discuss this with pio_masaki since he had a brick happen to him recently, and he is quiet knowledgeable with the procedures to try to recover from lost partitions or to verify that you are indeed bricked (lost GPT partition info ) .
stock rom
my tablet(a100)is doing much the same, its stock except for crosix swap-mod ,i plug into pc(win 7) and it says apx not installed..last nite it locked up while reading,..and well..i rebooted it and all i saw was the android..
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )
Hello All,
Due to my endless frustrations, this might be a long one so please bear with me!
So I purchased a Verizon Global HTC ONE M7 from the States, I am currently in Nigeria and the only thing that makes me sadder and more frustrated than the state of my phone right now is the incessant terror attacks in the country! Initially, almost everything worked fine when i popped in my new Etisalat sim card into the phone, except for the mobile hotspot (which just conveniently turns out to be the one of the top 3 most important features in a phone for me - probably the feature I use the most) this message kept popping up about how hotspot couldn't be used without a VZW sim, etc (also with the non-verizon sim warning when the phone boots up). I tried all I could, eventually deciding to flash a new ROM to clear out everything Verizon and start fresh.
Enter Viperone 6.2.0 - everything worked initially, but after a few weeks i noticed if I did anything like watch a youtube video or download something over a few MBs 90% of the time the data drops (no visible signs like changes from E to H or 3g or the likes, everything looks the same, just that the data stops), toggle mobile data on/off and data connection is back. It worsened and became more frequent over time. Upgraded to Viperone 6.2.1, no difference, so i figured its probably the viperone rom.
Enter Cyanogenmod - http://forum.xda-developers.com/ver...-oneplus-one-stock-rom-cm11s-verizon-t2857425 - and its the same exact issue from the beginning, so im guessing its not to do with the ROM at all (though there are one or two niggling issues with the ROM - cant change BBM display pic, etc)?! I've really tried to comb through the forum and see what makes sense that i could try without bugging y'all - I did a factory reset, wiped everything completely and its the same thing.
I've seen suggestions to similar issues like: flash stock recovery, update radio/firmware/kernel, flash back to custom recovery and some other things which are beginning to sound quite dangerous in my ignorance!! I did believe updating the firmware made sense but after digging deeper, i must honestly say i'm quite confused on what to do. what radio/firmware/kernel works with what software version, etc- most firmware that i've seen are 4.4.3 compatible, while this ROM is 4.4.4., some of them seem to be for stock ROMs only and a lot of other confusions.
So, I'm not gonna be a hero and brick my phone from trying to do what i do not understand, instead here i am, hat in hand, crying out for help after suffering for 3 months! Its really frustrating as, downloads break causing me to lose data, skype or MSLync calls always break and im beginning to look unprofessional to people! This is why I have decided to put up a post of my own specific to my case so i don't medicate for someone else's ailments. So please........ WHAT EXACTLY DO I DO??
PHONE DETAILS (typing it out as i've just realized on this ROM i can't take screenshots with Power+Home button combo anymore and can't be bothered at this point!!!)
ANDROID VERSION: 4.4.4
BASEBAND VERSION: 1.12.41.1112_2
KERNEL VERSION: 3.4.82-gfe09065; [email protected] #1; Wed oct 8 01:36:03 PDT 2014
BUILD DATE: SUN AUG 3 23:00:51 PDT 2014
BUILD NUMBER: CYANOGENMOD 11S v5 (Verizon)
SELinux status: Enforcing
Thanks
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Uzephi said:
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Click to expand...
Click to collapse
Thanks for the responses folks, i'll try out your suggestions and revert..
8100
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Mr HaRR said:
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Click to expand...
Click to collapse
FALSE ALARM FOLKS!!! I decided to attempt flashing the CM11 rom i just uninstalled and it worked. Turns out its a known issue with the .zip file for that rom - i am now re-downloading from another mirror. Meanwhile the Fastboot thing was just a driver issue - though i'm surprised because i had all the drivers installed on the system and have used fastboot successfully - anyway i reinstalled the drivers and all was well with fastboot again.
NB: Don't get tired of me just yet please!
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Mr HaRR said:
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Click to expand...
Click to collapse
If doing factory reset from stock recovery doesn't fix it, it is most likely a burned SIM. It has happened to me. (Average 150+ GB a month in data, so I burn em easily)
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
ccarr313 said:
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
Click to expand...
Click to collapse
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Mr HaRR said:
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Click to expand...
Click to collapse
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
dottat said:
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
Click to expand...
Click to collapse
HA! and now i feel :silly: !!
Bless your soul! i'll give it a go shortly...
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Boltrag said:
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Click to expand...
Click to collapse
First of all, roms from other phones are not compatible with phones other than what it was designed for. If you tried others, that's why it won't boot up. Secondly, if you read all the posting about how do install twrp, it also said there wasn't any way back EXCEPT for your backups. Unfortunately there is no factory images for the Razer phone released as of yet. If you are unable to restore from your backup (or skipped the step and didn't create one) your only choice is to attempt to restore via the backups Xshooter726 made and posted, and if they don't work, you need to wait till the factory images are released and we don't know when they will be out other then a vague "soon" from a community manager on their forums.
Boltrag said:
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Click to expand...
Click to collapse
If you're flashing roms for other Devices but now much experience do you have with flashing etc? Ignoring that fact unless backups from other devices work then youve no choice but to wait for razer to put up full factory images in January and flash those. Razer won't help you as you've voided your warranty.
Roxas598 said:
If you're flashing roms for other Devices but now much experience do you have with flashing etc? Ignoring that fact unless backups from other devices work then youve no choice but to wait for razer to put up full factory images in January and flash those. Razer won't help you as you've voided your warranty.
Click to expand...
Click to collapse
I had a decent bit, we only tried to flash another rom after we couldnt find the stock image, it was a last ditch effort.
Boltrag said:
I had a decent bit, we only tried to flash another rom after we couldnt find the stock image, it was a last ditch effort.
Click to expand...
Click to collapse
Well you're lucky none worked it could have made your problem a lot worse. When factory images release you can flash those if the backup doesn't work but until then you're out of luck unfortunately.
Side note if razer ask for imie etc don't give them it. Might be able to list the device as have being unlocked etc.