Related
Hello community!!
I'm new to the HTC/Incredible S world, I have a rooted/cfw LG P500 and now I bought this great phone. Problem is that I updated it to the last official version before this try.
So I went to the official site and I followed successfully the HTC site steps to unlock the bootloader (golden card?) and now I'm trying to follow the guide
http://forum.xda-developers.com/showthread.php?t=1385084
But I have some problems.
First of all clearly the revolutionary program doesn't work (HBOOT 2.0).
I booted to the bootloader (power+volume down) and I had the error "main version is older" then I copied on the SD card the file for the recovery PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip, I renamed it PG32IMG.zip, it loads it but when I press recovery it gives me an allert icon (the phone with a red triangle + red "!" ) and it does nothing.
I installed the SuperUser app like it is written in the post but when I type SU under the adb shell and it gives me "permission denied".
What could I do?
Is it even possible to downgrade it to a rootable/customable version?
If someone write a guide for rooting with the last update installed from original s-on step to step will be very util and a lot of people will be gratefull!
Inviato dal mio HTC Desire usando Tapatalk
Bootloader unlock and goldcard are 2 seperate things. Bootloader unlock is required at the moment for flashing recovery and superuser for rooting the phone.
Gold card is required for flashing another carriers rom.
Read this thread about recovery http://forum.xda-developers.com/showthread.php?t=1104765
After that you can enter recovery mode and flash a superuser zip file http://goo-inside.me/superuser/
My guide should be able to downgrade your rom and get s-off after that (if after researching you decide you require it) http://forum.xda-developers.com/showthread.php?t=1373697
Hope this helps
Thanks, I'm going to try this as soon as I can, I'll write back the results
edit:
It seems like I can't even pass the first step, the 4EXT Recovery Updater doesn't work, it crushes at EVERY menu item....
(I waited 5+minutes and I had the internet connection on).
I checked and the boot loader says "unlocked". Notice that my device is, of course, NOT rooted (at least for what I know for "rooted", it is still unlocked by the HTC official method)....
you need root to use the recovery updater.
download the recovery image and flash it in fastboot
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
sariel82 said:
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
Click to expand...
Click to collapse
Could I get a couple of screenshots to help with debugging please?
Sure, ASAP
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
edit:
It seems I cannot post the images, too noob ....
Anyway:
I had a photo of the phone in the custom recovery mode, another of the phone with the 4EXT recovery successfully flashing his recovery, another of the script of your post running with this message:
(no errors)
Do you have an unlocked bootloader from htcdev.com (I have)
y OR n:y
<waiting for device>
...
(bootloader) Lock successfully..
FAILED (status read failed (Too many links))
finished. total time: 0.239s
Note: run the RUU in fastboot mode
If all steps etc etc
Now if I try to run RUU NOT in fastboot mode I receive the message:
The Utility of ROM udating can't update the Android device.
Take a valid ROM updating Utility and try again
(I'm translating from Italian)
If I try to go to fastboot after running the script I need to go to hboot using volume down+power since you can go to fastboot only through bootloader and HIS first step is to check the bootloader file (am I right?)
so, since it is again LOCKED the custom boot file I was using PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed
doesn't work anymore and the old one neither so I have to unlock it again and it goes the loop......
So this is the situation, I hope I will be able to post some image soon...
sergiopat said:
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
Click to expand...
Click to collapse
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
sariel82 said:
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
Click to expand...
Click to collapse
OK, I thought you only wanted to root.
Thank you anyway
You don't need s-off for CFW's, just the unlocked bootloader. I cannot help you any further until I see screenshots as I'm getting lost in your descriptions. Ctrl prtscrn, paste in paint.
Well, I have the screenshots but I can't post web links in the forum (new user).
Let's see if I can flash some cfw in the mean time
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
sariel82 said:
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
Click to expand...
Click to collapse
After you flash a custom ROM in recovery, you have one last step to do to prevent the hang. You extract the boot.img file from the ROM's zip file and then manually flash it in FASTBOOT mode on the phone:
FASTBOOT flash boot [path to boot.img]
That totally solved the problem
Thank you ALL!!!
sariel82 said:
That totally solved the problem
Thank you ALL!!!
Click to expand...
Click to collapse
Hi,
Please list the methods you use from the start. I have also 2.3.5 and hboot 2.0. cant manage to downgrade, i always getting an error.
Thanks
htc developer site -> unlock bootloader
find and download this file:
PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio _20.2810.30.085AU_3805.06.03.16_M_release_199684_s igned.zip
copy it on the sd card and renamto to pg32IMG.zip
reboot in power+volume down mode
go in fastboot
from your pc use fastboot to flash this recovery:
http://forum.xda-developers.com/showthread.php?t=1104765
copy to sd card the superuser file:
http://goo-inside.me/superuser/
enter recovery mode and flash the zip
Then if u want to flash a custom rom you dont need to downgrade, just copy the zip into the sd card, flash it, copy on the sd card the boot.img you find inside the rom zip file and reboot in fastboot (power+volume down)
FASTBOOT flash boot [path to boot.img]
and reboot and the job is done!
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
Why can't you download an earlier firmware?
schmeggy929 said:
Why can't you download an earlier firmware?
Click to expand...
Click to collapse
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
schmeggy929 said:
i downloaded the asus firmware for 10.14.1.47. extract zip and you get a user.zip. extracted the boot.img. I fastboot erase boot, system, format system, data and cache(as you did)
fastboot -i 0x0B05 flash boot boot.img then
fastboot -i 0x0B05 flash system blob then
fastboot -i 0x0B05 flash system UL-K00C-US-10.14.1.47-user.zip
rebooted back into fastboot and bootloader showed 10.14.1.47 version.
Click to expand...
Click to collapse
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Ikkerens said:
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Click to expand...
Click to collapse
you are going to get that along with a few more errors. Wait until it is done. It will take like 10 mins and finish.
when it is done reboot in bootloader and you should see the version change.
schmeggy929 said:
you are going to get that along with a few more errors. Wait until it is done. I will take like 10 mins and finish.
Click to expand...
Click to collapse
You're getting this wrong, it does not do anything. The process immediately quits.
Ikkerens said:
You're getting this wrong, it does not do anything. The process immediately quits.
Click to expand...
Click to collapse
Ok when you get that message do you get a blinking curser?
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
lpdunwell said:
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
Click to expand...
Click to collapse
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Ikkerens said:
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Click to expand...
Click to collapse
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
lpdunwell said:
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
Click to expand...
Click to collapse
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Ikkerens said:
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Click to expand...
Click to collapse
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
lpdunwell said:
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
Click to expand...
Click to collapse
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Ikkerens said:
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Click to expand...
Click to collapse
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Snah001 said:
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Click to expand...
Click to collapse
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Ikkerens said:
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Click to expand...
Click to collapse
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
pelago said:
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Click to expand...
Click to collapse
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Snah001 said:
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
Click to expand...
Click to collapse
Already too late, it has been RMA'd, and then, I had nothing to flash it with.
Ikkerens said:
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Click to expand...
Click to collapse
Well I meant, what should a root user do to try and protect themselves against bricking their device like you did? Is it a matter of making sure that CWM or TWRP is on the device as a recovery partition? And are those available on TF701T yet?
Oh dear. That's a lot gone wrong.
Cwm is available and that works.
It's made by drgravy. I use it in my unbrick tut.
All i can say is, root --> cwm --> backup.
Sent from my GT-I9505 using xda app-developers app
That CWM wouldn't boot for me :/
So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !
doud1998 said:
So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !
Click to expand...
Click to collapse
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.
Hazou said:
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.
Click to expand...
Click to collapse
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me
doud1998 said:
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me
Click to expand...
Click to collapse
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.
Hazou said:
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.
Click to expand...
Click to collapse
I'm really sorry to annoy you for that but i don't get what you mean by "section E"
doud1998 said:
I'm really sorry to annoy you for that but i don't get what you mean by "section E"
Click to expand...
Click to collapse
I meant, in my signature under my post u can find within the link INDEX/GUIDE, ALL Things RAZR I under paragraph/ section E a link to all the firmwares available for the Razr I.
But in this case i will post the full link to the firmware site, here.
I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)
i tried to flash recovery_signed but i have the error
Checking fs on partition pds...
E:can't repaire partition pds
E:failed to mount PDS partition
doud1998 said:
I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)
Click to expand...
Click to collapse
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back
Hazou said:
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back
Click to expand...
Click to collapse
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)
+> i don't have any backup and i can't go to recovery , when it turns on it automaticly stuck to the ap fastboot menu
doud1998 said:
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)
Click to expand...
Click to collapse
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:
waj3k said:
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:
Click to expand...
Click to collapse
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?
doud1998 said:
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?
Click to expand...
Click to collapse
I know, I just uploaded Deodexed Retail Great Britain ICS:
Here you go. There should be a download icon at the top.
give me the right access (i'm [email protected])
Sorry, forgot to set it to public, should be fixed now.
so now i have to flash the boot.img or what? i'm not really sure what to do with this zip
You need to flash custom recovery and then you can install a zip.
Here is a tutorial on how to use recovery, if you're unsure.
i can't make works neither cwm nor twrp
doud1998 said:
So here is my problem, after trying to install a custom rom on my razr i, i may have broken something in the system
Click to expand...
Click to collapse
may i ask you what u have exactly done to install your "custom rom"?
1. Bootloader unlocked?
2. Custom Recovery installed?
3. How did you installed your rom?
4. Which custom rom?
Hi All,
I see a lot of people asking for stock stuff for the HTC One Mini 2, please find them here:
Stock RUUs - https://forum.xda-developers.com/one-mini-2/general/htc-one-mini-2-official-ruu-t3425930
BOOT IMAGE
Signed Boot Image : boot_signed.img for booting problems (FOR INTERNATIONAL/EUROPEAN DEVICES ONLY)
PROCESS
Enter bootloader and then enter fastboot and type the command :
Code:
fastboot flash boot boot_signed.img
fastboot reboot bootloader
Nandroid Backup for restoring to stock, I have used this, working fine (Can be restored through TWRP): https://www.androidfilehost.com/?fid=24052804347818782 (FOR INTERNAITIONAL/EUROPEAN DEVICES ONLY)
Stock Firmware: https://www.androidfilehost.com/?fid=95784891001615234
Stock Recovery: https://www.androidfilehost.com/?fid=24052804347822267 (Newer)
Stock Recovery: https://www.androidfilehost.com/?fid=95784891001615233
Original Page (German): http://www.handy-faq.de/forum/htc-one-mini-2-firmwaresammlung-ruus-otas-backups-t309020/
LINKS WERE WORKING WHEN I POSTED THEM, DOWNLOAD AT THE EARLIEST AS MAY BE THEY WONT WORK WHEN YOU NEED THEM, SO JUST DOWNLOAD AND KEEP.
STEPS TO RESTORE NANDROID BACKUP THROUGH TWRP:
- REBOOT AND ENTER TWRP, PERFORM A BACKUP (THIS WILL CREATE A TWRP BACK UP FOLDER WITH DEVICE SERIAL NUMBER IN THE SD CARD)
- DOWNLOAD AND EXTRACT THE NANDROID BACK UP FILE
- PLACE THE EXTRACTED FILES IN TO THE TWRP>BACKUP<DEVICE SERIAL NUMBER> FOLDER IN THE SD CARD
- RESTART THE DEVICE AND ENTER TWRP, CHOOSE RESTORE
- LOCATE THE FOLDER COPIED IN THE ROOT OF THE SDCARD
- SWIPE TO RESTORE
- FOR SOME REASON THE NANDROID BACKUP DOES NOT CONTAIN CALCULATOR, FLASH LIGHT WHICH CAN BE DOWNLOADED HERE: http://www.apkmirror.com/apk/htc-corporation/
THANK YOU
I cant install
Bear Grylls said:
I cant install
Click to expand...
Click to collapse
What is the exact problem you are facing when flashing the stock file. PLEASE EXPLAIN FOR BETTER UNDERSTANDNG.
ELSE YOU CAN TRY THE BELOW.
NB: I AM ASSUMING THINGS AND GIVING THIS INFORMATION, I AM NOT RESPONSIBLE FOR WHAT HAPPENS AS I DONT KNOW THE EXACT PROBLEM YOU ARE FACING.
Make sure device is 100% battery.
1st try this:
1-Download this file: [ https://drive.google.com/file/d/0B_1zjuazXSqbQ0p6NWtvRk9OMzA/edit?pli=1 ] and install in Windows (Run as Administrator).
2-Open Command window and type:
Code:
cd c:\adb
3-now on your device use Vol keys to choose and power key to select, and choose FASTBOOT
4-now download the attached file boot_signed.rar (extract the file in C:\adb folder)
5-type in the command window:
Code:
fastboot flash boot boot_signed.img
5-type in the command window:
Code:
fastboot erase cache
6-type in command window:
Code:
fastboot reboot
IF THIS DID NOT WORK, THEN TRY THIS:
Download this [ https://www.androidfilehost.com/?fid=95916177934555508 ] file and rename it to 0P8BIMG.zip and place it into the SD card (MMC Card), restart the device and let it boot into the HBoot menu.
Reboot device from the boot mode, if the device automatically reboot into the boot menu then it will start flashing the file automatically.
Good Luck, let me know how it went.
Try and let me know.
this is excellent, all in one place...
However, please forgive my ignorance in recovery/backup terminology (I hope it is not just me) but I get confused by the use of 'Nandroid' backup, Stock Rom, and .zip and .img files for flashing.
I have successfully used TWRP to flash the NostromoPop ROM, but have not been successful with any other .zip file supposedly a Stock ROM.
I have been hoping that somebody could put a rooted Stock ROM so that I can try it as a way to get around the KitKat blocks on writing to the SD card for some of my autosync apps.
Am I making any sense?
Many thanks if you can help
soundrediscovery said:
this is excellent, all in one place...
However, please forgive my ignorance in recovery/backup terminology (I hope it is not just me) but I get confused by the use of 'Nandroid' backup, Stock Rom, and .zip and .img files for flashing.
I have successfully used TWRP to flash the NostromoPop ROM, but have not been successful with any other .zip file supposedly a Stock ROM.
I have been hoping that somebody could put a rooted Stock ROM so that I can try it as a way to get around the KitKat blocks on writing to the SD card for some of my autosync apps.
Am I making any sense?
Many thanks if you can help
Click to expand...
Click to collapse
Hi,
As I understand you cannot flash a stock ROM with customer Recovery, as far as I know you need stock Recovery to flash a stock ROM, I remember trying stock ROM on TWRP but it failed, could be due to some other reason, I read somewhere it has something to do with file signatures.
As for SD write fix, you need to have root access other than that there is no fix for it, rooting with SuperUser Binary... I myself did want to try it now that I am back on stock but then I am greedy for Marshmallow (if they could fix that Loud Speaker issue) I am all in for Android M, I tried to get in touch with people on the Cyanogen Forums but no luck as I have not yet received verification email, tried so many times, no luck and as it seems there is no Marshmallow development on HTC One Mini 2....
I will wait and see how it goes...
If I am correct you can keep stock ROM and flash SU Binary and get root access and then install https://play.google.com/store/apps/details?id=nextapp.sdfix to get it done with, it ought to work, haven't tried myself...
The recovery image you gave seems a little broken, but the backup worked...thought I recommend a factory reset unless you want the system language to be weird...
hanro50 said:
The recovery image you gave seems a little broken, but the backup worked...thought I recommend a factory reset unless you want the system language to be weird...
Click to expand...
Click to collapse
Which recovery image have you used, I have flashed the newer version successfully, yes the backup worked and has non-English language as default.
The command:
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache
If you could elaborate a "little broken"
I maneged to reflash twrp from android, ok these is what happened, I flash it as a recovery image with twrp, when I reboot into recovery later then it just showed a picture of my phone with a red triangle icon in it, after a while my phone resets...and goes back to booting from the main installed os...
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
The name of the file is M8_MINI_UL_Stock_Recovery_2.19.401.2.img
I don't remember if I taped New or old
hanro50 said:
I maneged to reflash twrp from android, ok these is what happened, I flash it as a recovery image with twrp, when I reboot into recovery later then it just showed a picture of my phone with a red triangle icon in it, after a while my phone resets...and goes back to booting from the main installed os...
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
The name of the file is M8_MINI_UL_Stock_Recovery_2.19.401.2.img
I don't remember if I taped New or old
Click to expand...
Click to collapse
Hi,
I believe you flashed a recovery with another recovery, which I think is not the right way, the right way is to use the command to overwrite TWRP with stock recovery.
hanro50 said:
I maneged to reflash twrp from android, ok these is what happened, I flash it as a recovery image with twrp, when I reboot into recovery later then it just showed a picture of my phone with a red triangle icon in it, after a while my phone resets...and goes back to booting from the main installed os...
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
The name of the file is M8_MINI_UL_Stock_Recovery_2.19.401.2.img
I don't remember if I taped New or old
Click to expand...
Click to collapse
HI,
Just wanted to know if you are having any issues with low audio after restoring Android backup from TWRP, I feel my audio is way too low and cant be heard just if I am outside my room..
I didn't have any audio problems, it could just be you being used to cm's 3rd party BoomSound replacement
---------- Post added at 01:25 PM ---------- Previous post was at 01:21 PM ----------
Well that would exsplain why some elements of the stock recovery remained after I reflashed twrp with a app on my phone, e.g. it fixed the image I get when I hook my device up to power when it is turned off...before that it would just boot me into a unusable twrp homepage
The stock RUU file is corrupt! (tried 5 times now)
Where can I get a A stock flash or a ROM that is NOT ROOTED please?
I tried the 0P8BIMG.zip on SD card method and that did not work either.
Also, I thought the RUU file is meant to be an executable not a zip file. I'm confused...
niblettr said:
The stock RUU file is corrupt! (tried 5 times now)
Where can I get a A stock flash or a ROM that is NOT ROOTED please?
I tried the 0P8BIMG.zip on SD card method and that did not work either.
Also, I thought the RUU file is meant to be an executable not a zip file. I'm confused...
Click to expand...
Click to collapse
I doubt its corrupted, which OS are you running currently ?, when I tried it, it failed due to the installed stock ROM being newer than the one being installed and since I have S-ON I cant downgrade it...
You can Nandroid Restore the stock backup, I have personally tried and it works....
Another way to do it is to have the Nandroid Restore and then use Sunshine to S-OFF (as sunshine only works on stock or near-stock ROMs) and then flash with 0P8BIMG.zip, it should work then, just a thought...
Hi, thanks for these links & info. Just about to give this a go. But, what does boot_signed.img do?
pavsid said:
Hi, thanks for these links & info. Just about to give this a go. But, what does boot_signed.img do?
Click to expand...
Click to collapse
Its a signed boot file, meaning it flashes successfully should the device fail to boot or stuck on boot or in other words if the device does not boot and remains on HTC, this flashing this should solve your problem.
Hi all I have been directed here from another thread as I am looking to place a stock rom on my htc one mini 2 without bloatware, I have unlocked the bootloader and installed TWRP but the stock rom remains the same all I want is to install a rom via TWRP if at all possible. Is the 1gig one ok for that or will i need to completely put the stock recovery back on and the phone is unlocked to all networks if that makes any different
Thank in advance
The Watergod said:
Hi all I have been directed here from another thread as I am looking to place a stock rom on my htc one mini 2 without bloatware, I have unlocked the bootloader and installed TWRP but the stock rom remains the same all I want is to install a rom via TWRP if at all possible. Is the 1gig one ok for that or will i need to completely put the stock recovery back on and the phone is unlocked to all networks if that makes any different
Thank in advance
Click to expand...
Click to collapse
Hi,
Its not possible to flash stock rom via TWRP, plus you need to have S-Off.
The only way to go complete stock is to restore Nandroid Backup and then flash stock recovery.
TryllZ said:
Hi,
Its not possible to flash stock rom via TWRP, plus you need to have S-Off.
The only way to go complete stock is to restore Nandroid Backup and then flash stock recovery.
Click to expand...
Click to collapse
so is this the nandroid back up of a stock rom that I can use with the latest update for use with twrp and when I mean stock rom I mean a rom that has not been majorly altered to class it as a custom rom. I.e still has sense and no additional apps added
Again Thanks in advance
The Watergod said:
so is this the nandroid back up of a stock rom that I can use with the latest update for use with twrp and when I mean stock rom I mean a rom that has not been majorly altered to class it as a custom rom. I.e still has sense and no additional apps added
Again Thanks in advance
Click to expand...
Click to collapse
Hi,
Yes you will have to restore the Nandroid Backup, this backup is completely of a stock ROM, no edition, however it does not have some apps like the Calculator, Flash etc for some reason.
However I found the missing apps from here: http://www.apkmirror.com/apk/htc-corporation/
TryllZ said:
Hi,
Yes you will have to restore the Nandroid Backup, this backup is completely of a stock ROM, no edition, however it does not have some apps like the Calculator, Flash etc for some reason.
However I found the missing apps from here: http://www.apkmirror.com/apk/htc-corporation/
Click to expand...
Click to collapse
Excellent much appreciated for this right, so I need to first copy the nandroid backup to my Phones root and run TWRP and restore using the downloaded nandroid yes?
if yes could I please have the steps to put the stock recovery on with ADB commands as I really don't want to brick my phone (Yes I know you take no resposibilty etc) just happier to have as least the correct file names and adb commands.
And last I just copy the new stock RUU to my phone and install?
You help is as always greatly appreciated as no one seems to be ddoing anything anymore for this phone
Hi Guys,
My friend bricked his phone. Im trying to recover it. Its a VNS-L21.
I tried putting the stock rom on it using dload method from
https://boycracked.com/2016/09/13/official-huawei-p9-lite-vns-l21-stock-rom/amp/
and
http://huafirmware.com/8-firmware/16-huawei-p9-lite-vns-l21
but the upgrade fails everytime saying incompatible.
any help is appreciated :fingers-crossed:
My fix for the issue
malikusmanrasheed said:
Hi Guys,
My friend bricked his phone. Im trying to recover it. Its a VNS-L21.
I tried putting the stock rom on it using dload method from
https://boycracked.com/2016/09/13/official-huawei-p9-lite-vns-l21-stock-rom/amp/
and
http://huafirmware.com/8-firmware/16-huawei-p9-lite-vns-l21
but the upgrade fails everytime saying incompatible.
any help is appreciated :fingers-crossed:
Click to expand...
Click to collapse
Hey man, I got a problem just like you and this is the way I fixed it.
Download the Huawei update extractor:
https://forum.xda-developers.com/showthread.php?t=2433454
And use this to open your Update.app you already downloaded.
Extract the 'boot.img' and the 'system.img'.
Now you need fastboot, follow this tutorial:
https://www.xda-developers.com/xda-...tall-adb-and-fastboot-system-wide-in-windows/
Now open terminal/cmd/powershell and open the folder the boot.img and system.img you extracted are in.
Connect your phone in fastboot and run the following commands:
fastboot flash system [Extracted_System.Img]
fastboot flash boot [Extracted_Boot.img]
fastboot reboot
This resolved the issue for me, I hope also for you!
JatanX said:
Hey man, I got a problem just like you and this is the way I fixed it.
Download the Huawei update extractor:
https://forum.xda-developers.com/showthread.php?t=2433454
And use this to open your Update.app you already downloaded.
Extract the 'boot.img' and the 'system.img'.
Now you need fastboot, follow this tutorial:
https://www.xda-developers.com/xda-...tall-adb-and-fastboot-system-wide-in-windows/
Now open terminal/cmd/powershell and open the folder the boot.img and system.img you extracted are in.
Connect your phone in fastboot and run the following commands:
fastboot flash system [Extracted_System.Img]
fastboot flash boot [Extracted_Boot.img]
fastboot reboot
This resolved the issue for me, I hope also for you!
Click to expand...
Click to collapse
Hi Jatan,
Thanks for the reply. I tried that as well with a couple of stock images but all i got was a blank screen. Can you share the stock image that you used?
:good:
for most Stock images when i try to "Fastboot flash system d:\System.img" ( system.img is in D: in my case), i get this error
FAILED (remote: sparse flash write failure)
malikusmanrasheed said:
for most Stock images when i try to "Fastboot flash system d:\System.img" ( system.img is in D: in my case), i get this error
FAILED (remote: sparse flash write failure)
Click to expand...
Click to collapse
How did he brick it? What was he specifically doing (nougat update etc.)? Do you get the same error when you try and flash a boot image, stock recovery or other partitions?
Can you install twrp? If so, try wiping the system & boot partitions in twrp, then try flashing boot & system again in fastboot. If he'd updated to nougat, then you'll need to try and flash the rollback package first then dload a Marshmallow rom and go from there
I would suggest using this tool:
https://forum.xda-developers.com/p9/development/huawei-p9-eva-l09-eva-l19-eva-l29-tool-t3591358
to install this tool to unlock bootloader and install twrp.
After unlocking your bootloader everything on your phone is gone though.
Then in twrp you can try to repair your your partitians by going to wipe->advanced wipe->repair or change...
And thereafter continue with the steps is provided earlier or install a new rom, this is up to you.
I hope it fixes it for you.
colthekid said:
How did he brick it? What was he specifically doing (nougat update etc.)? Do you get the same error when you try and flash a boot image, stock recovery or other partitions?
Can you install twrp? If so, try wiping the system & boot partitions in twrp, then try flashing boot & system again in fastboot. If he'd updated to nougat, then you'll need to try and flash the rollback package first then dload a Marshmallow rom and go from there
Click to expand...
Click to collapse
Hi colthekid,
He just went nuts and wiped everything he could see in the twrp.
After that I have tried to write this via the method jatan suggested:
VNS-L21C185B360
from http://www.stechguide.com/download-huawei-p9-lite-b360-nougat-update/
still no boot.
JatanX said:
I would suggest using this tool:
https://forum.xda-developers.com/p9/development/huawei-p9-eva-l09-eva-l19-eva-l29-tool-t3591358
to install this tool to unlock bootloader and install twrp.
After unlocking your bootloader everything on your phone is gone though.
Then in twrp you can try to repair your your partitians by going to wipe->advanced wipe->repair or change...
And thereafter continue with the steps is provided earlier or install a new rom, this is up to you.
I hope it fixes it for you.
Click to expand...
Click to collapse
I'l try that and update.
i have twrp. repaired the partitions. did the flast via fast boot using the above method
"Now open terminal/cmd/powershell and open the folder the boot.img and system.img you extracted are in.
Connect your phone in fastboot and run the following commands:
fastboot flash system [Extracted_System.Img]
fastboot flash boot [Extracted_Boot.img]
fastboot reboot"
and still the same. It flashes the files fine. but at boot i get a black screen.
I think im using the wrong files. Can anyone please share the link for a full stock rom nougat , or a roll back from nougat to mm (i flashed this VNS-L21C185B360 latest)
or maybe i need to do write the oeminfo or something. Read it somewhere. not clear on what it is
malikusmanrasheed said:
I think im using the wrong files. Can anyone please share the link for a full stock rom nougat , or a roll back from nougat to mm (i flashed this VNS-L21C185B360 latest)
Click to expand...
Click to collapse
Maybe you need to continue this in the P9 Lite forum?
However, in the meantime, this should help you along!!
Firmware... https://forum.xda-developers.com/hu...huawei-p9-lite-firmware-compilations-t3517124 (pick a full MM rom)
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)
colthekid said:
Maybe you need to continue this in the P9 Lite forum?
However, in the meantime, this should help you along!!
Firmware... https://forum.xda-developers.com/hu...huawei-p9-lite-firmware-compilations-t3517124 (pick a full MM rom)
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)
Click to expand...
Click to collapse
This:
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)
solved my problem.
Putting the puzzle back again:
I think the genius removed the oeminfo along with everything else he could see in the twrp wipe menu.
I tried to put multiple firmwares on the device nougat ( as he updated) but the boot still showed blank.
As soon as i flashed the oeminfo --> then MM firmware, the device booted up.
Thank you so much everyone for your help. Really appreciate it :good::good::good::good::good::good:
Excellent! :good::good:
And I'm sure your friend is glad to have a working phone again!
Explains why dload wouldn't work as well. As far as I'm aware the update.app checks oeminfo to make sure the firmware is compatible. Hence if you want to debrand a phone to C432, you have to flash a C432 oeminfo before the C432 update.app will flash successfully. No oeminfo=no compatibility for anything!!!
hi,
please help unbrick my P9
I can't get into fastboot, the only one thing it boots is the eRecovery, (system partition damaged)
---------- Post added at 04:26 AM ---------- Previous post was at 04:11 AM ----------
konstwww said:
hi,
please help unbrick my P9
I can't get into fastboot, the only one thing it boots is the eRecovery, (system partition damaged)
Click to expand...
Click to collapse
somehow i managed to get to fastboot but trying to flash system get error
sending sparse 'system' (449861 KB)...
OKAY [ 14.749s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.142s
Update: To get into fastboot is very important that smartphone is connected via USB to PC, then Power-button and VolumeDown together till Phone gets into fastboot.
from there flash TWRP, and reboot to recovery, after that install full Update (Files and guideline is here in first post part 3 and 4 https://forum.xda-developers.com/p9/development/rom-huawei-p9-magic-rainbow-t3601064).
malikusmanrasheed said:
This:
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)
solved my problem.
Putting the puzzle back again:
I think the genius removed the oeminfo along with everything else he could see in the twrp wipe menu.
I tried to put multiple firmwares on the device nougat ( as he updated) but the boot still showed blank.
As soon as i flashed the oeminfo --> then MM firmware, the device booted up.
Thank you so much everyone for your help. Really appreciate it :good::good::good::good::good::good:
Click to expand...
Click to collapse
Can you please send me your full steps. I really need it