Related
Hi
I was flashing back to Stock from task650 to fix my gps. Well something blew up and when the phone reboots the screen goes black but I hear the AT&T start-up tune. Essentially I can't get to enable USB debugging to reflash. I can get to download or recovery, but there are no files to recover<?> and busybox never got installed.
What do I do now?
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
CZ Eddie said:
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
Click to expand...
Click to collapse
Yes I have stock recovery. Odin is of no use because it hangs waiting for the USB debug to respond. And i can't turn it on because the screen is black and I can't navigate
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
xBeerdroiDx said:
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
Click to expand...
Click to collapse
Thanks. I created an emergency tool kit on an SD, I wiped data, wiped cache and Davlik and formated system. Flashed the stock rom. When I rebooted it now hung at the Samsung Galaxy S III screen.
How do I get out of this mess?
Try wiping data and cache again in recovery
xBeerdroiDx said:
Try wiping data and cache again in recovery
Click to expand...
Click to collapse
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
BertMor said:
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
Click to expand...
Click to collapse
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
xBeerdroiDx said:
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
Click to expand...
Click to collapse
When it rains it pours. Now I can't get into recovery. I get the empty battery graphic cycling on and off, and its very warm to the touch. I think the battery is not charging.
I tried using Odin and flashed a stock rom but I kept getting verification errors and status 7 errors. Things just are not taking. I fear I've got a hard brick and I don't know what to do to fix it.
I appreciate your help
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
xBeerdroiDx said:
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
Click to expand...
Click to collapse
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
it might indeed be drained. leave it plugged in for a while and report back.
you were getting the error/status 7 messages after you flashed cwm back on it likely because the cwm wasnt up-to-date.
what was the last thing you tried before it stopped working altogether?
It gets really hot if I leave it plugged in. But it seems like I can get into recovery again. The last thing I flashed was CMW 6.0.3.1. But what is on it now is CMW 5.5.0.4
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
BertMor said:
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
Click to expand...
Click to collapse
xBeerdroiDx said:
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
Click to expand...
Click to collapse
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
BertMor said:
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
Click to expand...
Click to collapse
Well I think I managed it!. First I tried to install an update d/l'ed from Dropbox and that did nothing. Then I flashed an old .tar that was a rooted stock and it rebooted!
I tried editing the updater-script but I couldn't getit to save the changes properly.
Well I will now re flash the RM and CWM and hope for the best
Thanks for all your help, greatly appreciated
I was on stock Android and yesterday wanted to go for a custom rom. So went to TWM recovery, took a full backup and then I went in to Wipe and, instead of doing a factory rest, I went on did an Advanced Wipe and Format Data. (I think this has caused all the following problems. ) It cleared all the data on the phone.
Then i used adb push to send the custom rom to /sdcard and tried installing. But the install failed after a few seconds with the following error;
set_perm some changes failed
The last log entry was getting partition information or something.
(However installer log says, formatting system, cache and stuff was successful seconds before the error)
After trying and failing to install few roms, I went on to install the Stock again.
Used adb again to flash the stock. And amazingly it worked. Booting and working without any issues.
But still, when I’m trying to install a custom rom it gets failed in a while. After few trial and errors, I tried restoring my first backup before all this, restore was successful. But when I try to flash a custom rom again I ended up with the same error. Tried with both CWM and TWM.
I tried everything (I hope I’m wrong).
Currently my phone is in working condition with Stock Rom rooted and TWM recovery, kernel_FuguMod_20131015_r1172-4.3
Any idea guys? I hate the idea of having to live with the stock for the rest of my life.
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.
I'm having some issues flashing any ROM. TWRP will not wipe data, or internal SD
For some reason, when I go to wipe data and factory reset, TWRP will say it was successful, but nothing ever gets wiped. It will only wipe system if I choose to. I've gotten a ROM to flash but when it boots up, all of the old apps and user data are still there and it makes everything crash. I've gotten into settings to do a reset, it reboots into recovery, runs the script, and still nothing wipes.
What I have tried:
Old TWRP, newest TWRP
CWM (seems to wipe but it won't get past the note 2 screen after flashing anything)
Wiping with CWM, flashing TWRP, then flashing a ROM (still loops after the note 2 screen)
Is there a terminal command I can use in TWRP to manually wipe things?
Thanks for any help I can get, I've flashed so many phones I can't remember but I've never had this issue
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
audit13 said:
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
Click to expand...
Click to collapse
Well when it bootloops t the Note 2 screen, I have to flash a ROM with Odin to get it working again. I've flashed a stock ROM with Odin, flashed TWRP with Odin, tried the wipes and it never wipes anything... I'm lost...
Isn't there a format function in TWRP that is seperate from the factory reset or advanced wipes? I was also trying to find a terminal command to type in the terminal in TWRP... I'm a little stumped...
I'm sorry, I read that too fast... That may actually work, wipe it in the stock recovery, and just don't let it boot into the system before flashing other stuff... I'm gonna try that out... Thanks man, I'll post back about it...
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
audit13 said:
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
Click to expand...
Click to collapse
The stock ROM I used is I317-ODIN-UCUCNJ1-Stock without the booloader packaged in, I'm still on the old bootloader. It's 4.4.2
The ROMS I've tried to flash was
Cyanide (Error 7, says incompatible data, please wipe the phone)
Resurrection Remix (Error 7, says incompatible data, please wipe the phone)
Latest CM10 Nightly
I got CM10 and Resurrection Remix to flash a couple times, but the phone boots and all the old apps and data, including the AT&T ones are still there, and the system keeps crashing. Then I change the recovery to CWM because it seems to wipe, change back to TWRP, flash the ROM and gapps again, but it bootloops at the Note 2 screen.
Should I try the 4.1.1 ROM and CWM? Whenever I'm going from a stock TW to non-TW I like to format everything, data, cache, system, and internal SD, but of course TWRP won't wipe the data or the internal SD.
It's probably because the bootloader and modem are too old for the roms. Recent roms will need updated bootloaders.
Ok, I had some more time to mess around with this today and figured it out. I feel kind of dumb but oh well, I got it.
TWRP was already loaded on, so I went to messing with it again. The 'Swipe to factory reset' was not wiping the data, and there was the 'Format Data' button right there in front of me. I did the factory reset, format data, rebooted recovery, wiped dalvik, cache, and system, then flashed the ROM and everything booted up just fine.
Thanks for all of the help!
I tried Factory Reseting my phone earlier today through Recovery, It said everything was reset so I restarted my phone. My phone is now in a bootloop, it vibrates, shows the "erasing" screen, then the hidden LED light turns on and the screen goes black, then the phone does that forever. It's on the erasing screen for about 3 seconds before restarting. Trying to enter Recovery Mode just sends me back to the "erasing" screen.
Any help would be wonderful!
Were you completely stock? On a ROM? With custom recovery?
What steps did you use? Wipe data and factory reset? Did you wipe the cache partition?
If you were on stock, I would suggest you tried to wipe again. You could try to do it with ADB and fastboot if you are not able to access the recovery (which I don't think would happen if you're completely stock).
If you were not on stock or with a custom recovery, the easiest way to solve this would be to reinstall the ROM you were using.
victorhbm15 said:
Were you completely stock? On a ROM? With custom recovery?
What steps did you use? Wipe data and factory reset? Did you wipe the cache partition?
If you were on stock, I would suggest you tried to wipe again. You could try to do it with ADB and fastboot if you are not able to access the recovery (which I don't think would happen if you're completely stock).
If you were not on stock or with a custom recovery, the easiest way to solve this would be to reinstall the ROM you were using.
Click to expand...
Click to collapse
I was Stock ROM with root, I edited the build.prop file and rebooted the device, that’s when the issues began. I had TWRP installed and restored my backup of my phone from before I made any changed, this didn’t help anything (I was stuck on the “Your device is unlocked” screen). I restored the stock recovery and I now have the original recovery installed. Finally after some well timed button presses I am no able to access the Stock Recover, however if I try to side load a working ROM onto my phone it shows the percentage of the side load but then fails this:”
E:footer is wrong
I:verify_file returned 1
E:Signature verification failed
E:error 21
W:failed to read uncrypt status: No such file or directory
“
It’s a little late now, so I’ll be back tomorrow to do some more research.
Dubstepwolf123 said:
I was Stock ROM with root, I edited the build.prop file and rebooted the device, that’s when the issues began. I had TWRP installed and restored my backup of my phone from before I made any changed, this didn’t help anything (I was stuck on the “Your device is unlocked” screen). I restored the stock recovery and I now have the original recovery installed. Finally after some well timed button presses I am no able to access the Stock Recover, however if I try to side load a working ROM onto my phone it shows the percentage of the side load but then fails this:”
E:footer is wrong
I:verify_file returned 1
E:Signature verification failed
E:error 21
W:failed to read uncrypt status: No such file or directory
“
It’s a little late now, so I’ll be back tomorrow to do some more research.
Click to expand...
Click to collapse
Did you factory reset already?
I don't think you can sideload a ROM with stock recovery.
Don't try to flash anything with stock recovery, better go back to TWRP.
PD: If when going to TWRP you slid the "swipe to allow modifications", that's what caused the bootloop, as it made modifications to the partitions. Or so I read on a guide here.
victorhbm15 said:
Did you factory reset already?
I don't think you can sideload a ROM with stock recovery.
Don't try to flash anything with stock recovery, better go back to TWRP.
PD: If when going to TWRP you slid the "swipe to allow modifications", that's what caused the bootloop, as it made modifications to the partitions. Or so I read on a guide here.
Click to expand...
Click to collapse
Thinking back again I guess it didn’t make much sense trying to flash a rom through Stock Recovery. Yes I did Wipe the Cache partition and then I Wiped data/factory reset through Stock recovery, all I did in TWRP was restore everything from the backup.
*An hour later*
So I was able to get TWRP installed again. Unfortunately when I try to restore from a backup I made with TWRP before messing with anything it restores with no errors or warnings, but when I reboot the system it gets stuck on the "Your device is unlocked and cannot be trusted" screen. Probably sounding stupid saying this, but shouldn't a restore of a backup be straight forward?
*Another hour later*
I was able to get ToxycOS 3.0 installed and running, but personally I don't like it and want to go to Motorola's Software... now I just need to fix whats wrong with my restore.
Dubstepwolf123 said:
Thinking back again I guess it didn’t make much sense trying to flash a rom through Stock Recovery. Yes I did Wipe the Cache partition and then I Wiped data/factory reset through Stock recovery, all I did in TWRP was restore everything from the backup.
*An hour later*
So I was able to get TWRP installed again. Unfortunately when I try to restore from a backup I made with TWRP before messing with anything it restores with no errors or warnings, but when I reboot the system it gets stuck on the "Your device is unlocked and cannot be trusted" screen. Probably sounding stupid saying this, but shouldn't a restore of a backup be straight forward?
*Another hour later*
I was able to get ToxycOS 3.0 installed and running, but personally I don't like it and want to go to Motorola's Software... now I just need to fix whats wrong with my restore.
Click to expand...
Click to collapse
Why not fastboot install stock firmware?
Isn't that available, here?
pizza_pablo said:
Why not fastboot install stock firmware?
Isn't that available, here?
Click to expand...
Click to collapse
In the end I was able to install the Stock Moto Z2 Play firmware... I hate when people don't include the fix in their answers for other people, but currently I am unable to post any links because they are on a different device. I'll get back later with the links.