Develop Bugs

JBX Help

Please help. I have flashed the kernel provided in the thread (by Supervenom) and now i cannot get into recovery to flash rom. What should i do? Please help! My phone is just black screen. It gets the pxp logoand than black...

akcentstyle said:
Please help. I have flashed the kernel provided in the thread (by Supervenom) and now i cannot get into recovery to flash rom. What should i do? Please help! My phone is just black screen. It gets the pxp logoand than black...
Click to expand...
Click to collapse
http://www.box.com/s/pcslaphpx4sqx3mi2bc9
Download this, put it in your fastboot directory, rename it to recovery.img, then on your command line, enter...
Code:
fastboot boot recovery.img
This will live boot a recovery for the play, this is when you flash JBX.
Just to be safe, do the following after getting into recovery.
*Wipe Data/Factory Reset
*Wipe Cache Partition
*Wipe Dalvik Cache
*Format /system
*Install JBX
*Power off phone and enter fastboot mode
*Flash Supervenom Kernel
*Boot into recovery using the method I gave you
*Wipe Data, Cache, Dalvik Cache
*Boot into phone
For JBX, I think you were supposed to flash the rom first, then the kernel, but you're guaranteed to run the recovery with this method. That's why I never use the recoveries that come with kernels.

[Q] TripnDroid problems

Hi
I just flashed Tripndroid CM10 0.28 by
flashing boot.img through fastboot usb
going into recovery and factory resetting
then flashing the rom
and then reboot system
When it boots up it says gapps stopped and sais unfortunately setup wizard has stopped, have I done something wrong here?
How can I get it to work?

you have not wiped cache...
1. download rom and gapps,transfer them to root of SD card
2. extract boot.img(the kernel) from ROM zip and place it in fastboot folder
3. go into bootloader, FIRST flash the boot.img in fastboot(does the screen say FASTBOOT USB when u connect the phone to the PC?)
4. go into recovery, then FULL WIPE-factory reset, erase cache and dalvik cache.
5. then flash the ROM.
6. boot into the rom.then again enter into recovery and then flash gapps.
do the above steps in the same order all over again....it should work

[Q] Hardware navigation buttons do not work on some ROMS after clean install

Hi,
I'm finding with some ROMs (SlimBean, ProBAM, CM Domination) after an install on my HOX that the hardware navigation keys don't work anymore. I have to enable the soft keys in order to be able to use the phone - obviously not desirable as it wastes screen space.
I've done a crapload of googling, searching the forums, etc and can only find info on disabling the buttons. Is there some obscure setting I am missing somewhere?
The process I use is the same as is recommended on most of the other posts:
- fastboot erase cache
- fastboot flash boot boot.img (of the rom I am installing)
- in CWM, delete userdata, format cache/dalvik
- install rom
- reboot
When the phone boots up - straight away the capacitive buttons no longer work.
Reflash with a different ROM (CM10, Blade) and they are fine.
Can anyone help?
Thanks

I've had that happen on probam/slimbean if I don't flash Gapps.
Sent from my HTC One X using Tapatalk 4 Beta

sinkster said:
I've had that happen on probam/slimbean if I don't flash Gapps.
Sent from my HTC One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
Aha - thanks for the suggestion, I'll give it a go. From memory I probably hadn't installed Gapps at that stage since I was just checking the ROM out..
thanks man

Gapps would have no bearing on such a problem, coincidence. And to prove a point, gapps are included in the ProBAM rom and the fault still occurred. I would suggest you change slightly the method of wiping between roms.
From CWM recovery, format data,system and cache. Then mount usb storage and format the sdcard to fat32 from your pc or laptop, but change the allocation unit size from 16 to 32 in the dropdown. Then while usb is mounted copy over the rom, and gapps if required. Just to be sure wipe dalvik cache in recovery then reboot the bootloader and flash boot image in fastboot and fastboot erase cache.
Very important to erase cache in fastboot.
Once that is done, back to recovery and flash rom and gapps if required and your done. This is the method I use every day and never have a problem.
Just re-read OP and I noticed that you fastboot erase cache before flashing boot image, you must also erase cache after flashing boot.
sent from my shorts

nogotaclue said:
Gapps would have no bearing on such a problem, coincidence. And to prove a point, gapps are included in the ProBAM rom and the fault still occurred. I would suggest you change slightly the method of wiping between roms.
From CWM recovery, format data,system and cache. Then mount usb storage and format the sdcard to fat32 from your pc or laptop, but change the allocation unit size from 16 to 32 in the dropdown. Then while usb is mounted copy over the rom, and gapps if required. Just to be sure wipe dalvik cache in recovery then reboot the bootloader and flash boot image in fastboot and fastboot erase cache.
Very important to erase cache in fastboot.
Once that is done, back to recovery and flash rom and gapps if required and your done. This is the method I use every day and never have a problem.
Just re-read OP and I noticed that you fastboot erase cache before flashing boot image, you must also erase cache after flashing boot.
sent from my shorts
Click to expand...
Click to collapse
notgotaclue, thanks for the detailed response - I will most definitely give this a go when I get some time over the next few days. Cheers mate

@nOtgotaclue: I went through your process and it did work for me with CM10 Domination - but not ProBam or Slimbean, they still had the same problem with hardware keys not working.
I've ended up flashing another kernel (TripNDroid v15 AOSP) and it has fixed the issue (for SB at least, yet to try it on ProBam).
Thx again for your help

Can't delete a rom (CM11) to install new one

****edit: It appears that the option "format /system" which is tucked away in a sub menu did the trick and erased the rom.
I am trying to completely delete a rom I have installed which is CyanogenMod 11 but it seems to stay no matter what, or I'm not doing it right.
First I go into recovery with the power+vol down and choosing recovery.
I have ClockworkMod 5.8.1.5.
From there I choose the wipe data/factory reset and also the wipe cache partition and wipe dalvik cache.
Then I choose the install zip from sd card to install Blackout_ICS_Incredible_v4.0.zip
After following the installer instructions and rebooting it goes back to CM11...
Any ideas how to wipe CM11 from my device?
Thanks :good:

Netanel1 said:
****edit: It appears that the option "format /system" which is tucked away in a sub menu did the trick and erased the rom.
I am trying to completely delete a rom I have installed which is CyanogenMod 11 but it seems to stay no matter what, or I'm not doing it right.
First I go into recovery with the power+vol down and choosing recovery.
I have ClockworkMod 5.8.1.5.
From there I choose the wipe data/factory reset and also the wipe cache partition and wipe dalvik cache.
Then I choose the install zip from sd card to install Blackout_ICS_Incredible_v4.0.zip
After following the installer instructions and rebooting it goes back to CM11...
Any ideas how to wipe CM11 from my device?
Thanks :good:
Click to expand...
Click to collapse
Try formatting with fastboot.
Boot your device into fastboot and type these commands
Code:
fastboot devices
Just to be sure ur devic is connected
Code:
fastboot format system
Code:
fastboot format data
Code:
fastboot format boot
If the above doesnt work, susbtitute
Code:
format
with
Code:
erase

4EXT Recovery 1.0.0.6 R2
try changing the recovery via bootloader, download latest 4ext recovery zip then rename it to PD98IMG and place it to your root directory of your sdcard. Then go into bootloader it will automatically detect zip file and will ask you for update, press volume up to start the update, reboot and your done. After flashing new recovery go into recovery and then wipe/format from there format all partitions except sd card. When done go back to main menu and select info to see the free space/size of all partitions.
Device: HTC Desire HD
ROM: CM11 M8.1
Recovery: 4EXT 1.0.0.6 R3 build 8
If it helped you then pressing then press the thanks button.

Are these steps correct to flash custom rom in 2020?

-use miunlock to unlock bootloader
-put phone on fastboot mode
-type 'fastboot flash antirbpass dummy.img'
-type 'fastboot flash recovery twrp-3.3.1-0-whyred.img'
-type 'fastboot reboot'
-reboot to recovery using phone
-copy gapps & custom rom to phone
-wipe system, data, dalvik, cache
-flash rom
-flash gapps
-reboot
I am currently on MIUI Global 9.5.19.0 with locked bootloader.
Is this method correct? I dont know which guide is outdated right now and which is not. Sorry if this is asked too many times.

Yes this is correct but i want to make some changes in your guide
1. Use orange fox recovery as it is better than twrp and it won't give u any error which u may encounter using twrp.
2. U can use fastboot boot *recovery* to push recovery file and flash its zip after entering recovery (it doesn't need any kind of dummy file flash)
3. Wiping vendor is also there
Thank you

oh ok so basically these are the edited steps to follow now:
-use miunlock to unlock bootloader
-put phone on fastboot mode
-boot twrp using 'fastboot boot XYZ.img'
-flash orange fox zip from twrp
-reboot to orange fox recovery from twrp
-wipe system, data, dalvik, cache, vendor
-flash latest firmware
-flash custom rom
-flash gapps
-flash magisk
-reboot
correct?
thanks a lot btw!

? correct and u can use 9.4.25 firmware as it is best (atleast for me)

Should I follow the same procedure if my phone is on 11.0.3.0?

scarednewbie said:
Should I follow the same procedure if my phone is on 11.0.3.0?
Click to expand...
Click to collapse
Now most of the customs support the new pie firmware.
1. Unlock bootloader.
2. Reboot to bootloader
3. Boot to orangefox recovery using
fastboot boot recoveryname.img
4. Copy the orangefoxrecovery.img(extract the orangefox zip) to device storage using the booted orangefox in step 3.
5. Flash orangefox permanently from the copied img file using the booted recovery.
4. If you are planning to use miui don't reboot without flashing magisk. It may reset the recovery to default miui recovery.
6. Enjoy flashing custom roms after wiping(not formating) system, data, cache, vendor etc. No need to format data if you need file ssystem encryption. Formating data from recovery will remove encryption.

niyas90 said:
Now most of the customs support the new pie firmware.
1. Unlock bootloader.
2. Reboot to bootloader
3. Boot to orangefox recovery using
fastboot boot recoveryname.img
4. Copy the orangefoxrecovery.img(extract the orangefox zip) to device storage using the booted orangefox in step 3.
5. Flash orangefox permanently from the copied img file using the booted recovery.
4. If you are planning to use miui don't reboot without flashing magisk. It may reset the recovery to default miui recovery.
6. Enjoy flashing custom roms after wiping(not formating) system, data, cache, vendor etc. No need to format data if you need file ssystem encryption. Formating data from recovery will remove encryption.
Click to expand...
Click to collapse
Orange fox recovery has aggressive stock recovery deactivation so magisk is not necessary