Related
Something went wrong during an ODIN revert to stock, and now when I plug in the phone to the computer or wall it shows the battery charge image for a few seconds, then it says the "Samsung Vibrant" splash and goes straight into recovery mode. I've tried holding down the volume keys, adb doesn't recognize the device. IDK wtf to do. Any help would be so appreciated I'll paypal the person a six pack that can help me fix this.
When it goes into recovery mode it says...
Movi_check Start...!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
Movi_check already executed!!...
Movi_checking done!..
E:Can't mount /dev/block/stl11
(invalid argument)
E:Can't mount /dev/block/stl11
(invalid argument)
did you try holding down volume up/down, and just plugging it into your computer?( so you can get into download mode)
So I just got off the phone with Tech Support, luckily I'm still under warranty and my recovery screen says "Android System Recovery" and not ClockworkMod Recovery. They went through the "Master Reset" and that didn't work, obviously, because I tried that. I also tried every other thread to get into download mode and Odin the original rom/kernel/recovery to no avail. They agreed to send me a new phone free of charge, added on the insurance and shipping is now free. Luckily my girlfriend didn't tell them what really went down haha. "Oh well he rooted his phone and then tried to un-root it and ended up turning it into a paper weight." So now I just sit and wait. Next time I'm not using any other outside write ups to try and reflash a recovery on the vibrant. After I get the OTA (if it ever comes) I'll root it again just to remove the bloatware like I did the first time. But with Clockwork you can't get the OTA, or so it said, so I'll just be patient and wait it out. To anyone else who is stuck in recovery and can't get it into download mode, or flashed the euro version, just call T-Mo tech support and say you downloaded an app and rebooted and voila stuck in recovery. On the downside, I have to wait 5-7 business days (not including weekends or holidays though) for my new one in the mail. So let this be a lesson learned to everyone, read read read and if all else fails, lie.
Its not as easy doing things on the Vibrant as it was with the good old Gangster 1 (G1).
Also, I only tried this because Rom Manager said I still had ClockworkMod Recovery instead of the stock recovery after I did the proper forum.xda-developers.com/showthread.php?t=734475, You don't need to flash the root update as the CSC, I guess there could be a non-root update.zip to use, but There was a guide I followed the first time that only used the PIT and PDA files, which put it back to stock but still had ClockworkMod Recovery on it. If it didn't, Rom Manager was lying to me.
red96turbols said:
So I just got off the phone with Tech Support, luckily I'm still under warranty and my recovery screen says "Android System Recovery" and not ClockworkMod Recovery. They went through the "Master Reset" and that didn't work, obviously, because I tried that. I also tried every other thread to get into download mode and Odin the original rom/kernel/recovery to no avail. They agreed to send me a new phone free of charge, added on the insurance and shipping is now free. Luckily my girlfriend didn't tell them what really went down haha. "Oh well he rooted his phone and then tried to un-root it and ended up turning it into a paper weight." So now I just sit and wait. Next time I'm not using any other outside write ups to try and reflash a recovery on the vibrant. After I get the OTA (if it ever comes) I'll root it again just to remove the bloatware like I did the first time. But with Clockwork you can't get the OTA, or so it said, so I'll just be patient and wait it out. To anyone else who is stuck in recovery and can't get it into download mode, or flashed the euro version, just call T-Mo tech support and say you downloaded an app and rebooted and voila stuck in recovery. On the downside, I have to wait 5-7 business days (not including weekends or holidays though) for my new one in the mail. So let this be a lesson learned to everyone, read read read and if all else fails, lie.
Its not as easy doing things on the Vibrant as it was with the good old Gangster 1 (G1).
Also, I only tried this because Rom Manager said I still had ClockworkMod Recovery instead of the stock recovery after I did the proper forum.xda-developers.com/showthread.php?t=734475, You don't need to flash the root update as the CSC, I guess there could be a non-root update.zip to use, but There was a guide I followed the first time that only used the PIT and PDA files, which put it back to stock but still had ClockworkMod Recovery on it. If it didn't, Rom Manager was lying to me.
Click to expand...
Click to collapse
Rom manager doesnt replace samsungs recovery. There is an update.zip that is placed in your root that allows you to get to clockwork recovery by simply reinstalling packages in samsung recovery. Clockwork recovery may still be flashed, but if you remove or replace that update.zip, the only way otherwise to get to it would be through rom manager. Which obviously isnt an option for you.
Sent from my SGH-T959 using XDA App
wildklymr said:
Rom manager doesnt replace samsungs recovery. There is an update.zip that is placed in your root that allows you to get to clockwork recovery by simply reinstalling packages in samsung recovery. Clockwork recovery may still be flashed, but if you remove or replace that update.zip, the only way otherwise to get to it would be through rom manager. Which obviously isnt an option for you.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Dang. Because when I opened CW it said "Current Recovery: ClockworkMod Recover 4.x.x.x, last version: ClockworkMod Recovery x.x.x." So I guess CW wasn't even on there, so I bricked it for no reason. If I just removed the update.zip it would have just been fine? Because it kept saying "You can't receive the OTA with your current ROM, please contact ROM author." Which is why I decided to reflash to stock un-rooted rom. I had also had a 6 pack and 2 jager bombs so hahaha fsck it. I'm getting a new one and will read when I'm un-ability impaired. Thanks for the note though.... but I also renamed the update.zip to 2.1rootupdate.zip, would that matter to CW or not? Because it kept saying no matter how I reflashed that CWR was still on there...
Did you try to flash 2.2 by any chance? Easy way to fox your problem is just adb reboot. It will boot up your phone past the recovery screen, and then you can use odin to get back to stock.
Sent from my Samsung Vibrant
red96turbols said:
Dang. Because when I opened CW it said "Current Recovery: ClockworkMod Recover 4.x.x.x, last version: ClockworkMod Recovery x.x.x." So I guess CW wasn't even on there, so I bricked it for no reason. If I just removed the update.zip it would have just been fine? Because it kept saying "You can't receive the OTA with your current ROM, please contact ROM author." Which is why I decided to reflash to stock un-rooted rom. I had also had a 6 pack and 2 jager bombs so hahaha fsck it. I'm getting a new one and will read when I'm un-ability impaired. Thanks for the note though.... but I also renamed the update.zip to 2.1rootupdate.zip, would that matter to CW or not? Because it kept saying no matter how I reflashed that CWR was still on there...
Click to expand...
Click to collapse
There is no updated rom available. That function of rom manager is currently unused by vibrant devs. It allows them to make updates to roms and streamline the process, but they simply move on to the next rom. Renaming the update.zip that is used to root to whatever it is is ok for cw recovery, but once you have clockwork recovery flashed since it doesnt replace samsung recovery. When something goes wrong you need its update.zip it puts in root to stay right where it is. By reinstalling packages in samsung recovery is the only way to get to clockwork recovery when you cant load up the phone. If that update.zip is gone or renamed, you're s.o.l.
Sent from my SGH-T959 using XDA App
So if I had kept that update.zip file that CW put on, chances are I could have fixed it? Since I clicked the "Repartition" check box on Odin, would it have even mattered? I used the 512.pit file and the Phone file from the "Unroot" thread by Koush I believe. That worked wonderful, and then I did it a second time and I think something went wrong.
Here's what's happenning.
- Device was rooted using HTC unlock method with HB00t 1.5
- Was running Synergy Rom
- Wanted to get latest OTA from Sprint so I followed the steps from another thread :
http://forum.xda-developers.com/showthread.php?t=1447839&page=2- Went through steps and unlocked my device again
Used file from post #16
- Did my updates, unlocked device, booted back into HBoot
- Decided I would try the Infected Eternity Rom this time so I followed those steps as stated in their thread. Did a clean flash. Flashed Superwipe, flashed data ext optimizer tool, flashed eternity rom w/ 3.5 sense
- after message said installation was complete, i got error message when i went back to main menu in recovery:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lastçlog
E:Can't open /cache/recovery/last_log
- device wouldn't boot once I rebooted from CWM. It would hang a the HTC white screen, then reboot again, keeps repeatedly doing this.
- Then I rebooted back in HBoot by pressing Vol Down and Power buttons. Went to recovery, flashed Synergy rom. Install was fine, still can't boot up device. Having the same issue. Device would hang at HTC white screen and continue to cycle on and off trying to reboot.
- Rebooted back to HBoot by pressing Vol Down and Power buttons. Went into recovery with CWM, restored my back up. Everything went fine except I got message:
sd-ext.img not found. Skipping restore /sd-ext.
As of right now, I can still boot into HBoot. I've tried reflashing Synergy rom again, but still nothing.
From my search, it says that based on my error message:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lastçlog
E:Can't open /cache/recovery/last_log
It could be a HW or SW issue.
Phone is still under HTC warranty, if I need to return it, what do you say to support department?
Thank you.
Have you tried flashing through fast boot through a usb connection? I know the h boot 1.5 are tough to do when you need to change kernals which is what happens when you got to a 3.5 Rom. I had some trouble too if you open recovery through fast boot and do everything that way all should be good.
Edit: as long as you can get into recovery I think you'll be okay.
I can definitely still get into recovery and HBoot. So I would assume those are good things.
Read another thread suggesting to use TWRP instead of CWM.
Will try both flashing with fastboot from usb and twrp and see if that helps.....
If anyone else have other suggestions,
fastbook using android sdk...
it's never bricked unless it won't turn on.
next time, don't try to fix it if it aint broken.
Unlocking via htc will require you to follow the following. The kernel can't be written unless you follow the directions below which can cause the issue you stated.
http://forum.xda-developers.com/showthread.php?t=1239821
Just let us know what happens it is most likely just a kernal problem. Look up how to do the fast boot to make sure it works right. Fingers crossed.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I had an error like that once before. I believe I had to format my sd card. I also formatted my sd-ext partition. Hopefully you have a backup of your sd card so you can try doing that. Of course you'd need to take your sd card out, and use a card reader to format it using your computer.
Sent from my HTC Evo 3D using Tapatalk
That's not a brick a brick is where you can't even get into hboot tho if your slick enough you could still fix a bricked phone lol
cobraboy85 said:
next time, don't try to fix it if it aint broken.
Click to expand...
Click to collapse
Actually, the reason for wanting to switch over to a different ROM was because with the Synergy rom, I was getting random reboots. Sometimes as much as 3 times a day. Other times, once or twice a week only. It seemed to be an issue that was never really addressed as it's still being asked in their thread now a days. So wanted to see if the Eternity Rom was more stable.
Back to the OP, just wanted to be clear that when I refer to rebooting back into recovery, I am not simply booting into HBoot and then selecting the "recovery" option on the menu. I am aware that I cannot use this method as I have Hboot 1.5. I am using a CMD window to fastboot the recovery program (either TWRP and CWM).
In my cmd window, I change into the propper directory with all my files. Then use commands:
adb reboot bootloader
fastboot boot recovery.img (used: fastboot flash recovery "FILE" to flash onto device)
And then I flash the zip files from there on.
In any matter, was able to get Synergy up and running again. For some reason, I couldn't get it working with CWM but was able to do so with TWRP.
Still getting the occasional random reboot. Have had it up and running for a day now and already one random reboot just a couple hours ago.
Still can't get Eternity w/3.5 Sense running though. So I have a quick question in regards to that. In following the steps on their thread:
http://forum.xda-developers.com/showthread.php?t=1277431
step 5 indicates that I need to copy over the boot.img file once I extract the rom.zip file to the same folder I used to unlock. However, I found two boot.img files under the Kernel folder. Which one do I use? Actually tried both and both gave me the same results (hangs at the HTC white screen and cycles on/off).
Note: the boot.img were found under sub folders "Shooter" and "Shooteru" in the kernel folder.
kyaj9 said:
Actually, the reason for wanting to switch over to a different ROM was because with the Synergy rom, I was getting random reboots. Sometimes as much as 3 times a day. Other times, once or twice a week only. It seemed to be an issue that was never really addressed as it's still being asked in their thread now a days. So wanted to see if the Eternity Rom was more stable.
Back to the OP, just wanted to be clear that when I refer to rebooting back into recovery, I am not simply booting into HBoot and then selecting the "recovery" option on the menu. I am aware that I cannot use this method as I have Hboot 1.5. I am using a CMD window to fastboot the recovery program (either TWRP and CWM).
In my cmd window, I change into the propper directory with all my files. Then use commands:
adb reboot bootloader
fastboot boot recovery.img (used: fastboot flash recovery "FILE" to flash onto device)
And then I flash the zip files from there on.
In any matter, was able to get Synergy up and running again. For some reason, I couldn't get it working with CWM but was able to do so with TWRP.
Still getting the occasional random reboot. Have had it up and running for a day now and already one random reboot just a couple hours ago.
Still can't get Eternity w/3.5 Sense running though. So I have a quick question in regards to that. In following the steps on their thread:
http://forum.xda-developers.com/showthread.php?t=1277431
step 5 indicates that I need to copy over the boot.img file once I extract the rom.zip file to the same folder I used to unlock. However, I found two boot.img files under the Kernel folder. Which one do I use? Actually tried both and both gave me the same results (hangs at the HTC white screen and cycles on/off).
Note: the boot.img were found under sub folders "Shooter" and "Shooteru" in the kernel folder.
Click to expand...
Click to collapse
gotcha. and is it eternity 3.0?
I have been running 1.4.2 with absolutely no issues now for 4 weeks. running Chad's RLS09 kernel that was pulled at the beginning of this month
you should give that set up a shot man. most reliable rom in my opinion.
k2buckley said:
I had an error like that once before. I believe I had to format my sd card. I also formatted my sd-ext partition. Hopefully you have a backup of your sd card so you can try doing that. Of course you'd need to take your sd card out, and use a card reader to format it using your computer.
Sent from my HTC Evo 3D using Tapatalk
Click to expand...
Click to collapse
The only back ups I have when I first rooted the device.
As long as formatting the SD card doesn't mean I am losing anything vital to the operation of the device, I would have no issues with having to put everything back on manually.
cobraboy85 said:
gotcha. and is it eternity 3.0?
I have been running 1.4.2 with absolutely no issues now for 4 weeks. running Chad's RLS09 kernel that was pulled at the beginning of this month
Click to expand...
Click to collapse
No it's the 3.5. I wanted to try the one with Sense 3.5.
For the good news!!! Finally got it to work. Backing up my apps with Ti Back up as I am writing this.
The only difference I did this time around was that after flashing Superwipe, I DID NOT flash the optimizer tool.
In all my other attempts, whether with TWRP or CWM, I was also flashing the optimizer after flashing Superwipe. Don't know if that was the actual cause or not with the install, but that was the ONLY step I did not do this time around.
From what I read, the optimizer is suppose to make the rom run faster because of the ext 4 partition. So my question now that I have up and running is will NOT having it flashed have any significant results?
On another thought, I did flash the optimzer as needed when I re-flashed Synergy. Does this carry over to the new rom or was I suppose to do again also for Eternity?
In any matter, thank you to all who helped. I will run Eternity for a week or so and see how stable it is first before trying anything else.
EDITED NOTE: Perhaps it should also be noted that I did download the latest build of Eternity also beforing getting it flashed and finally getting it running. Build 180. The file I couldn't get running was build 155.
OK...less than an hour into the rom and already experiencing some issues. It could be my flashing...but anyways.
When I try to run apps that require SU, it's saying that I the device is not rooted.
Could this simply be a case of a bad flash or am I missing something? Again, this is only apps that generally, would ask for super user permission. All other apps (games, etc) works fine.
Also, I do have the SU app updated to the latest version and it's visible in the APPS drawer.
To be specific, when I run the Adfree Android app, I get: "Fatal Error: Unable to get root"
Also, when I run MSL Reader, I get error: Couldn't find the superuser binary in any known path. Are you sure you are rooted?
kyaj9 said:
OK...less than an hour into the rom and already experiencing some issues. It could be my flashing...but anyways.
When I try to run apps that require SU, it's saying that I the device is not rooted.
Could this simply be a case of a bad flash or am I missing something? Again, this is only apps that generally, would ask for super user permission. All other apps (games, etc) works fine.
Also, I do have the SU app updated to the latest version and it's visible in the APPS drawer.
To be specific, when I run the Adfree Android app, I get: "Fatal Error: Unable to get root"
Also, when I run MSL Reader, I get error: Couldn't find the superuser binary in any known path. Are you sure you are rooted?
Click to expand...
Click to collapse
k I'm gonna help you out a little bit here...
re-download rom.
before you flash, wipe data twice, and cache twice.
under recovery settings, format system.
flash superwipe.
flash rom.
don't use titanium backup.
don't use ext4 data optimization tool.
you still have problems after that, then use a different rom.
and if you get the SU error, reboot to recovery and under advanced options or whatever, select "fix permissions"
It seems like you have a partitition issue on your internal or external memory in your case i think your internal memory is having trouble try black rose and associated partition tool to fix your partition schema
cobraboy85 said:
k I'm gonna help you out a little bit here...
re-download rom.
before you flash, wipe data twice, and cache twice.
under recovery settings, format system.
flash superwipe.
flash rom.
don't use titanium backup.
don't use ext4 data optimization tool.
you still have problems after that, then use a different rom.
Click to expand...
Click to collapse
cobraboy85 said:
and if you get the SU error, reboot to recovery and under advanced options or whatever, select "fix permissions"
Click to expand...
Click to collapse
Making sure I wiped out everything was the first priority I took. I did re-download the rom just to be sure it was a good download also.
Can't seem to get 3.5 version working propperly, but I did get 3.0 version up and running. Have had it for a couple days now with no issues so just gonna stick with that. Wanted to try out the sense 3.5 first, but the fact that there's no 4g support for it yet means I am probably better off with just using the 3.0 Sense.
Thanks for your help....
mahmutmuratdemir said:
It seems like you have a partitition issue on your internal or external memory in your case i think your internal memory is having trouble try black rose and associated partition tool to fix your partition schema
Click to expand...
Click to collapse
Not familar with Black Rose....but if I am not mistaken, isn't that just a HBoot for the Nexus 1?
yes it is made for nexus one to flash higher andrid versions but i think it can be used in some other models for partitioning internal memory
Sent from my Nexus One using XDA App
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
boneyarsebogman said:
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
Click to expand...
Click to collapse
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
es0tericcha0s said:
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
Click to expand...
Click to collapse
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
es0tericcha0s said:
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
Click to expand...
Click to collapse
I've wiped the Caches and Dalvik Cache and can't seem to find "Fix Permissions". I did some searching and it seems this feature was removed from CWM? I'm running v6.0.3.7 of CMW.
When I try to format the system, it says
E:format_volume failed to unmount "/system"
Error formatting /system!
Weird, they did take it out. Koush said it was a placebo. Which normally I would take as law, if it weren't for many times I have ran fix permissions and it caused apps that were force closing to not force close anymore. But whatever, if you wanna try, flash this: http://db.tt/9aWdF8Rp. It'll either help fix something, or do nothing. Won't make it any worse. If it can't mount to format though, it's either or a bug with CWM for your device, or after factory reset, reboot recovery and try again. But you really don't want to wipe /system unless you have a nandroid or another rom on your storage that is accessible.
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
boneyarsebogman said:
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
Click to expand...
Click to collapse
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
es0tericcha0s said:
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
Click to expand...
Click to collapse
Mine is the P2-6011.
Swear if we get this working, never changing anything ever.
Yes, the bootloader is unlocked.
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
es0tericcha0s said:
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
Click to expand...
Click to collapse
If I ever meet you I definitely owe you a drink. Did exactly as you said and everything (from what I can tell) is working.
It's one of the things I love about Android phones - unless you do some serious damage to it physically, for the most part it is fixable.
So, thanks button isn't enough - you saved me giving up and buying a new phone
*Hi Five* Glad all is well!
But yea, I do this for a living. Seriously. Helping people on here is how I stay sharp. lol
getting a gateway 504 error from link to firmware, would love to get this update working as i keep getting a notification on phone saying update available but it wont work
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
Can you post the link of the CM 10.2 rom For huawei P2.
I search for a long long time. but still dosnt found a rom.
Thx
Sorry for digging this up but does someone have the stock ROM of the P2? Im stuck like the fella who started this thread and havent found the stock ROM anywhere.
Thanks for the attention.
So, maybe someone can help me out here. I wanted to install Kit Kat Killer. This is what happens:
Rooting Process
1. I used Odin to install the root automatically.
2. I verified the root.
3. SuperUser and BusyBox installed.
4. Used Odin to install TWRP.
Recovery
1. Booted into TWRP.
2. Accidentally forgot to Nandroid Backup.
3. Wiped internal data, wiped everything else except SD Card.
4. Went to install Kit Kat Killer. Got some failed messages about some usb folder being unable to be mounted.
5. Rebooted phone. Re-downloaded everything and moved to SD.
6. Still fails.
Google time...
1. Downloaded some files from the links/forums I came across. None of these two files will flash through Odin, saying FAIL!
a. N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar
b. N900PVPUBMI3_N900PSPTBMI3_N900PVPUBMI3_HOME.tar
2. TWRP can't be added through ODIN anymore as far as I know. I was using version
Now...
1. TWRP is gone.
2. Phone is stuck in "ODIN MODE" for recovery (?).
3. I can't get past the Samsung Galaxy Note 3 screen.
4. When I get the yellow triangle about needing Kies3 for an emergency firmware repair, it does NOT recognize my phone. Yes, I am using Kies 3. It says I am using an unsupported phone.
5. It does say SW REV CHECK FAIL.
I am at a total loss here. I know it's a soft brick, but for the life of me, I can not figure out what to do next.
Thanks for all your help!!
Just got it back into TWRP mode. It keeps saying:
"E: Unable to mount /usbstorage"
Then when it tries to install KitKatKiller, it checks for the MD5 (on the SD too in the same directory), it says FAIL. I think this whole issue is based on the usbstorage thing.
Right now, I am going to download the latest Sprint stock ROM and see if I can flash it in TWRP. This will take at least 50 minutes to get going (30 for download/20 for file transfer). So plenty of time for you guys to jump in and say otherwise
Really, I appreciate all of your help!!! I am sure I made a n00b mistake. I had no real problems with my GSIII or EVO 4G once I got the hang of things
I think you guys can close this thread. I am not sure what the hell happened, but I wiped my SD card after copying the KitKatKiller ROM to another folder on the internal SD. I had forgotten to include the MD5 file in the same folder as well, but it finally installed. Right now, the phone is showing KitKatKiller logo spinning and booting up, so I presume the phone will be fine from this point, and if not, I will use Kies 3 to return it to stock and give it a try again. Again, you can close this thread, I feel like an idiot but it all worked out for some odd reason. I'm still not sure why I was getting "unable to mount usbstorage" errors.
Thanks again for everyone taking a look!!!!!!
jacobmiw said:
I think you guys can close this thread. I am not sure what the hell happened, but I wiped my SD card after copying the KitKatKiller ROM to another folder on the internal SD. I had forgotten to include the MD5 file in the same folder as well, but it finally installed. Right now, the phone is showing KitKatKiller logo spinning and booting up, so I presume the phone will be fine from this point, and if not, I will use Kies 3 to return it to stock and give it a try again. Again, you can close this thread, I feel like an idiot but it all worked out for some odd reason. I'm still not sure why I was getting "unable to mount usbstorage" errors.
Thanks again for everyone taking a look!!!!!!
Click to expand...
Click to collapse
Glad you figured your issues out. Just popped into tell you that twrp fails mounting USB because it's looking for an external USB. Not to worry its supposed to fail unless you have a USB drive plugged in through an otg cable.
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
OnlyEYEShine said:
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
Click to expand...
Click to collapse
What's the radio version that is installed? Should be viewable on the bootloader screen at the top. That will help determine which RUU you need to get back to running again.
http://www.androidruu.com/getdownlo...50.20_10.40.1150.04_release_324846_signed.exe
If it matches the numbers/letters after the Radio_ part there, then that is the file you need. Let me know, and I can download it for you and extract the rom.zip from the exe and upload that. Then you can use fastboot commands to install it on the phone. If your radio version does not match that, please post and we'll see if there are other options.
I don't believe that flashing another rom would work right now since all the storage and such got wiped, but it might be possible to use adb while in recovery to push a rom to the internal storage and install it and then use fastboot to install the boot.img from the rom in bootloader mode since you are S-On.
es0tericcha0s said:
What's the radio version that is installed? Should be viewable on the bootloader screen at the top. That will help determine which RUU you need to get back to running again.
http://www.androidruu.com/getdownlo...50.20_10.40.1150.04_release_324846_signed.exe
If it matches the numbers/letters after the Radio_ part there, then that is the file you need. Let me know, and I can download it for you and extract the rom.zip from the exe and upload that. Then you can use fastboot commands to install it on the phone. If your radio version does not match that, please post and we'll see if there are other options.
I don't believe that flashing another rom would work right now since all the storage and such got wiped, but it might be possible to use adb while in recovery to push a rom to the internal storage and install it and then use fastboot to install the boot.img from the rom in bootloader mode since you are S-On.
Click to expand...
Click to collapse
Hey there , i ended up making a 2nd thread, in the HTCONE section.. I am currently trying a fix that someone just posted. http://forum.xda-developers.com/htc...date-issue-t2898480/post55889272#post55889272 I will try your fix next, if this does not work =0) Thanks again !! DEFINETLY APPRECIATE IT !!
IF mod can close this thread to avoid confusion, it would be appreciated.