Develop Bugs

[Q] BootLoader is Loading Damn Slow? Searching for some Zip...

Hi Guys,
Since the time I Flashed the 4Ext Recovery 2.1, I am having very slow Bootloader..
When I power off my Phone and click Power + Menu to enter Bootloader I get this message on HBOOT at statu
Searching for PBDIA99.ziip
No image Found!!
Searching for PBDIAG99.nhh
No Image Found!!
Searching for Pxxxx.zip
Wrong Image!!
...........
........
Click to expand...
Click to collapse
This process like takes 30-40 secs now.. at first this screen used to appear for a second or two... but now its taking hell lot time and slow...
There is no .zip file in SDcard...
Whats wrong?

it always does that "search" for those files so don't worry about it, but never takes THAT long.. if you're S-OFF try flashing a new Hboot, could help.
If you're not S-OFF, then S-OFF using this, get different Hboots from here and check the MD5's with the tool attached - always check md5 of critical files before flashing as you can brick your phone.

bortak said:
it always does that "search" for those files so don't worry about it, but never takes THAT long.. if you're S-OFF try flashing a new Hboot, could help.
If you're not S-OFF, then S-OFF using this, get different Hboots from here and check the MD5's with the tool attached - always check md5 of critical files before flashing as you can brick your phone.
Click to expand...
Click to collapse
actually I had done S-OFF some 2 months back and it was working fine.. The $Ext recovery i flashed is also working fine... takes atleast 10 secs to show the Recovery screen but still shows...
But it was after flashing this 4Ext recovery I got this error of Slow booting... it never hapened before it..
BTW I had flashed the recovery using Terminal Emulator... At first I tried using .zip file by lacing in SD card but it didnt work so I extracted the recovery.img file and flahed with terminal emulator...
Can it be possible that 4Ext recovery is causing this error...

not entirely sure... but you could always try flashing a different recovery.. try the one from my signature and put it where in the tools folder of your android sdk for ease..
Code:
cd\
cd android-sdk/tools
fastboot erase recovery
fastboot flash recovery recovery-RA-desire-v2.0.0-CM.img
you can use cmd or use fastboot commander.. whichever is easier for you

jjdoctor said:
actually I had done S-OFF some 2 months back and it was working fine.. The $Ext recovery i flashed is also working fine... takes atleast 10 secs to show the Recovery screen but still shows...
But it was after flashing this 4Ext recovery I got this error of Slow booting... it never hapened before it..
BTW I had flashed the recovery using Terminal Emulator... At first I tried using .zip file by lacing in SD card but it didnt work so I extracted the recovery.img file and flahed with terminal emulator...
Can it be possible that 4Ext recovery is causing this error...
Click to expand...
Click to collapse
Maybe when you was trying to flash the recovery with PB99IMG.zip in HBOOT you then forgot to delete the file and it keep detecting it and trying to flash?
Just my 5 cents.

bortak said:
not entirely sure... but you could always try flashing a different recovery.. try the one from my signature and put it where in the tools folder of your android sdk for ease..
Code:
cd\
cd android-sdk/tools
fastboot erase recovery
fastboot flash recovery recovery-RA-desire-v2.0.0-CM.img
you can use cmd or use fastboot commander.. whichever is easier for you
Click to expand...
Click to collapse
If i just Place the Stock Hboot PB99IMG_stock.zipfrom alphrev site (after renaming to PB99IMG.zip) and enter Bootloader.. will it flash the Hboot auto?
and after flashing do I loose my ROM and all apps?

jjdoctor said:
If i just Place the Stock Hboot PB99IMG_stock.zipfrom alphrev site (after renaming to PB99IMG.zip) and enter Bootloader.. will it flash the Hboot auto?
and after flashing do I loose my ROM and all apps?
Click to expand...
Click to collapse
yes, just make sure to put it in the root of your sdcard. you "wont" lose all your data but you may be put into a bootloop because of the partition changes so do a nandroid backup

bortak said:
yes, just make sure to put it in the root of your sdcard. you "wont" lose all your data but you may be put into a bootloop because of the partition changes so do a nandroid backup
Click to expand...
Click to collapse
Hmmm... Don't think there will be partition changes since its same Stock Hboot I am reflashing...
Got to make backup now...

jjdoctor said:
Hmmm... Don't think there will be partition changes since its same Stock Hboot I am reflashing...
Got to make backup now...
Click to expand...
Click to collapse
oh yeah true, but it's still got practise to have a nandroid backup just in case, so you don't loose your data

SOLVED
Thanks to jjdoctor, this was solved for me (was taking 2 mins plus for each of the 4 checks, totalling aprox 12mins for bootloader to run) by formatting the sdcard in my phone using 4ext recovery. I took a nandroid, copied off the sdcard contents, formatted the card (ext4 and fat32), and then restored the card contents, and then restored the nandroid. Works perfectly now.
jjdoctor fixed his/hers by creating the partitions using gparted on PC and then re-formatting in the phone, but I just formatted it straight on the phone. Hope it help someone else.

[Q] Serious problem after flashing new Hboot - Need quick help [solved]

Hey everyone,
I just did something wrong i guess...I had CM7r2 Hboot and wanted to switch to the Oxygen Hboot in order to use the Oxygen ROM. So i downloaded the Oxygen Hboot, checked and verified the MD5sums, opened android flasher, chose the oxygen Hboot image and flashed it like I did with the CM7r2 before.
Problem now is that i can't boot into bootloader when holding Vol down+Power. instead the phone reboots into Recovery (Ext4) again and again and again. the recovery simply reloads all the time...
Because I can't boot into bootloader I can't flash the old Hboot or anything. And i can't use recovery because it reloads all the time
I am seriously f***ed and don't know what to do know!
Any help will be highly appreciated. I do have android-sdk and adb tools on my PC but never used them. If that is of any help...
I am pretty nervous now and afraid I broke me phone Please help!
Edit: Now it suddenly worked and i can get into bootloader. phew...that should make things easier ^^ It says Oxygen R2, so the flashing process worked. What should i do now? Maybe flash a new/different recovery? Try booting the recovery again? Don't wanna mess it up now that i got back into bootloader..
My original plan was installing the new hboot, wipe everything and clean install...

Get fastboot commander (it's a much better program, but requires SDK and JDK, links on my guide)... when you've got it working then:
Open FBC, go to the "misc" tab and select
-recovery
-boot
-system
-data
-cache
and click "erase chosen partitions"
Then use it to flash a new recovery.
Meh forget this, easier and faster method below...

Thanks for the quick reply. Did you see my edit in first post? Is your procedure then still necessary?
From your troubelshooting guide i guess my recovery is somehow corrupted, right? So flashing a new recovery using android flasher ( i am used to it and would save me time working myself into fastboot commander) should do the job, roght?

Mahlzahn said:
Thanks for the quick reply. Did you see my edit in first post? Is your procedure then still necessary?
Click to expand...
Click to collapse
if you're paranoid (and I would be) then yes lol
Actually you can just do it with cmd, it'd be easier... unpack the attached file into c:\
open cmd and type: (make sure you boot into fastboot mode)
Code:
cd\
fastboot erase recovery
fastboot erase boot
fastboot erase system
fastboot erase userdata (or fastboot erase data, can't remember which)
fastboot erase cache
Then use android flasher and flash a recovery (whatever one you want)..
then flash oxygen
This is just to be on the safe side btw, maybe your recovery screwed itself or something.. That's at least what I'd do anyway.. I mean if it works normally then you may not need to do anything, but I'd just be paranoid lol.

Ok, I did everything as you said, entered the cmd lines and flashed the current clockworkmod version as well as Oxygen. ROM booted and is working fine so far.
Thank you very much for your help!

Okay so i want this Oxygen ROM too. I am currently on the cm7/r2 hboot.
Would you recommend I move to another hboot then flash this rom?

gyak88 said:
Okay so i want this Oxygen ROM too. I am currently on the cm7/r2 hboot.
Would you recommend I move to another hboot then flash this rom?
Click to expand...
Click to collapse
If the hboot requirement for Oxygen ROM is oxygen hboot, then it is recommended to change the hboot. It should work without change of hboot but you are wasting 45mb which you can use as internal data storage.

If you are on Cm7r2, you can also add more apps to the Rom zip (Simply put the apk's in the system/apps folder) in order to use these 45mb and maybe leave a little space for themes, addons, customizations in case you want something like this. With Oxygen Hboot i couldnt even flash a UOT.zip because there's no more space. So I'd recommend Cm7r2 for anyone using Oxygen together with themes etc.

[Q] free beer if you fix my one x!

Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)

oh and ....
ALSO I've googled the problem and tried all of the options I can find which could help - please don't just send me a link to a page because i can guarantee I've probably already tried the solution and failed. When I boot into recovery, I can't use adb push to send files to the phone because it says it's not connected even if i try the option for mount data, or mount storage - the only time windows seems to manage to aknowledge it's existence is on the fastboot screen -
lazclark said:
Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)
Click to expand...
Click to collapse

Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app

thanks!
wow that was a quick reply - yes I've flashed the cm boot img and erased the cache - which version of CWM is the latest? - When you say mounting as USB storage is fixed, do you mean that windows will be able to see the device and write files to it?
(I'm really sorry for asking these questions - the problem is that I know a BIT about how android works but not as much as I should do)
treebill said:
Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse

Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't

This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!

sorry hope i'm not wasting your time!
I ran the command as follows :-
fastboot flash boot boot_signed.img
(I got the img file from the ruu )
I'm not 100% sure if it worked, but at that stage I didn't see any errors
Michealtbh said:
Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't
Click to expand...
Click to collapse

CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache

thanks!
I'll give it a go - to be honest i don't insist on using cm10 at all - i just wanted to see what jellbean was like and it seemed like a reasonable way of achieving that.... i'd be quite happy with any decent rom if it can fix the lag problems i have and some of the other issues.....
great tutorial by the way! - once my phone has charged up again I'll try it
ORStoner said:
This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!
Click to expand...
Click to collapse

ahhhh!
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
BenPope said:
CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache
Click to expand...
Click to collapse

Thanks.
I use CM10 myself at the moment because of the aesthetics, but because of the amount of ram and battery it uses I wish I had stuck with ARHD.
Come October we should see Jellybean ARHD which will have great features like USB OTG without a powered hub.

lazclark said:
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
Click to expand...
Click to collapse
Mount as USB not working on that version, also charging not working either. It was not a great release in terms.of features, but it was updated quickly, that's quite an.old version now.
Do you know which tutorial you followed? It really needs updating, there are a lot of people on this old version struggling more than they need to.

Right, first you're going to flash a recovery which allows you to mount USB storage. Either cwm or TWRP, download the recovery.img and flash through fastboot using fastboot flash recovery rocoveryname.img.
Download a new rom and extract the boot.img from it. Flash that boot.img using the usual fastboot method.
Now boot into the new recovery, connect to your pc and mount USB storage from the option in recovery. Copy over the rom you downloaded. Unmount USB storage. Now do a full wipe through the menu in recovery - format /data, /system and /cache. Now flash the rom and reboot

Stuck in Recovery

Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,

nodnarb said:
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
Click to expand...
Click to collapse
Try this, reformat your sdcard fat32 with a pc. Then place only this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip on the sd in no folders (Do not rename). Boot to hboot (vol down + power), it should find the file and prompt you to press vol up to install. I think your issue with the ruu before was that you were trying to flash an older version than you already have installed. If that dosent work try fastboot flashing cwm again, and see if it can mount the sd then.

Thread moved. Please post all questions here in the correct section of the forum.
Thanks
AvRS

Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app

shivaagarwal1 said:
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
You'll probably get better help in the Incredible S section. This is for just the plain olé Incredible.

[Q] MIUI Rom gone wrong

okay so heres what happened.
I have an international htc one x that is indeed rooted with no roms installed.
I did create a back up and then tried to install the MIUI rom (but I dont really know where that is on my phone. I know I made one with rom manager. I dont have any backups on my computer though)
It worked, however, it didnt have wifi or data signals so i went back to try again.
I opened my bootloader screen. For the record, it is unlocked and hboot is version 1.73 if that helps.
I wiped cashe/data/delvic everything and even factory reset and installed the MIUI RD rom now hoping it would have a difference.
The darn thing got stuck on the MIUI bootloader for hours.
I did the same thing again a few times, sometimes in different orders and then it passed on and another screen came saying 'starting apps'. That got stuck for hours too.
Now I don't have any other roms on my phone, just the MIUI RD. The original miui just vanished too, i dont see it anymore. Also, when I put my USB wire to the phone and connect it to the pc, I cant transfer newer files into it. So this is all I have access to on my phone apparently.
I tried flashing a boot.img and a couple kernels but no luck. I've been trying to do this for all day and this is my first time so I don't know much about it.
I've been googling and somethings say to open cmd and type but i keep getting 'fastboot is not recognized as an internal or external command'
Currently, its not stuck at either the MIUI screen or the Starting Apps. but just the HTC logo screen and not going past.
I don't really want to install any new roms considering i've worked really hard to get this to work and I really want it now more so.
How do i fix this? I want to use this rom.

flash philz recovery (http://forum.xda-developers.com/showthread.php?t=2240646), usb mounting should work on that, then:
steps to install ROM
1. bootloader version should be 1.3x
2. copy ROM to SD Card
3. copy boot.img INCLUDED in the ROM zip to fastboot folder
4. flash the boot.img in fastboot
5. in recovery, wipe system/data/cache/everything
6. flash rom
7. restart

but how exactly do i put it on my phone? my computer isnt detecting my phone when i connect it? im sorry im not exactly an expert on this.

Go to recovery - mounts and storage - hook up the usb cable - tap the last option in the mounts and storage list and wait a few minutes. It won't be mounted instantly

ok i flashed the philtz recovery but when i flash the boot.img it says:
Finding update package
Opening update package
Installing update
installation aborted
for reference: http://forum.xda-developers.com/showthread.php?t=1957490
thats the rom i used and i flashed the boot.img flasher thats right above the download link
edit: also i tried just flashing the rom again and im still stuck on the HTC screen.
its not even going to the miui screen or starting apps anymore. :[

Boot.img must be flashed via fastboot. Not via recovery !

ok, i looked up how to fastboot, downloaded sdk files and i moved the boot.img into the fastboot folder and i opened command prompt there and wrote fastboot flash boot boot.img but i keep getting:
'fastboot is not recognized as an internal or external command'
what did i miss?
EDIT: ok, so the fastboot folder i got from the page didnt work so i used a different fastboot folder, dragged the .boot there and now it worked! finally passed the screen and wifi is connecting!
thank you!

Good, thanks to @tomascus. He summed it up real nice
Cheers