First off, I don't know if this is the perfect place for this thread so I apologize in advance.
I have a HTC Evo 4G LTE and I accidentally wiped everything with TWRP. It can boot to the bootloader/fastboot menus and TWRP no problem, but I can't install anything. Maybe i'm just doing everything in the wrong order. Both the SD card and the Internal SD cards have been formatted to what they're supposed to be (caused me a bit of trouble at first). My phone is set to S-On, which is a pain in the ass, because from what I understand I can't turn it off to flash a new ROM without an OS, which I don't have. Every time I attempt to install the stock ROM for my device the phone restarts when attempting to install the kernel, included in the ROM. I borrowed my friend's identical phone, rooted it and installed TWRP, created a backup, moved the backup to my phone's ext SD card and attempted to recover off of that but my TWRP can't find any of the files, but they show up just fine with the file explorer.
I've properly srewed myself. Any advice?
windowpuncher said:
First off, I don't know if this is the perfect place for this thread so I apologize in advance.
I have a HTC Evo 4G LTE and I accidentally wiped everything with TWRP. It can boot to the bootloader/fastboot menus and TWRP no problem, but I can't install anything. Maybe i'm just doing everything in the wrong order. Both the SD card and the Internal SD cards have been formatted to what they're supposed to be (caused me a bit of trouble at first). My phone is set to S-On, which is a pain in the ass, because from what I understand I can't turn it off to flash a new ROM without an OS, which I don't have. Every time I attempt to install the stock ROM for my device the phone restarts when attempting to install the kernel, included in the ROM. I borrowed my friend's identical phone, rooted it and installed TWRP, created a backup, moved the backup to my phone's ext SD card and attempted to recover off of that but my TWRP can't find any of the files, but they show up just fine with the file explorer.
I've properly srewed myself. Any advice?
Click to expand...
Click to collapse
Since you are s-on you need to flash the rom twice.
BD619 said:
Since you are s-on you need to flash the rom twice.
Click to expand...
Click to collapse
I am new to ROM flashing, I just kind of got thrown into it, lol. Please elaborate? I'm assuming flashing is installing the rom with TWRP. I flash the rom, wipe cache/dalvik, then flash again? I'll try it then post results in a minute.
Result: Doesn't work, when it says "installing Kernel, please wait...", it stays on that message for a minute or so then the phone attempts to reboot into a nonexistant OS, effectively stopping itself so I have to restart into TWRP again with no progress made.
I think you want to let it reboot in between the two flashes. I have no idea why it makes a difference, but it does.
Sent from my EVO LTE using XDA Premium 4 mobile app
Read this:
http://forum.xda-developers.com/showthread.php?t=2443108
Some Sense ROM's include a kernel installer to help facilitate flashing while S-on. You'll need to check the ROM OP and see. Otherwise the kernel can be flashed via fastboot. For more info hit the top link in my sig.
Sent from my HTC device
fizbanrapper said:
I think you want to let it reboot in between the two flashes. I have no idea why it makes a difference, but it does.
Sent from my EVO LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It can't. It reboots while attempting to install the kernel then freezes because there's no OS to boot to.
Try flashing the kernel first. Extract the boot.img file from the ROM zip archive using your computer. Then, with the phone connected to the PC via USB, boot into the bootloader and go to fastboot. It should change to "fastboot USB". Then use the fastboot tool from a command prompt to verify connectivity and flash the kernel.
To verify connectivity, type fastboot devices. You should see your device's serial number of its connected properly.
To flash the kernel, type fastboot flash boot boot.img. If the boot.img file and fastboot executable are in different directories, you'll need to include the path to the file. Or just put them in the same directory.
Once you've flashed the kernel, try flashing the ROM through recovery again.
Sent from my EVO using Tapatalk
CornDogg said:
Try flashing the kernel first. Extract the boot.img file from the ROM zip archive using your computer. Then, with the phone connected to the PC via USB, boot into the bootloader and go to fastboot. It should change to "fastboot USB". Then use the fastboot tool from a command prompt to verify connectivity and flash the kernel.
To verify connectivity, type fastboot devices. You should see your device's serial number of its connected properly.
To flash the kernel, type fastboot flash boot boot.img. If the boot.img file and fastboot executable are in different directories, you'll need to include the path to the file. Or just put them in the same directory.
Once you've flashed the kernel, try flashing the ROM through recovery again.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Doesn't work. I can plug my phone in all I want but it will never change to fastboot usb. It stays in fastboot just fine and I can still boot TWRP, but there's no fastboot usb. I've reinstalled drivers and tried 32 bit LiveCD ubuntu. I may need to install firmware on this stupid phone.
From the main bootloader screen, you're pressing the power button on fastboot to go into fastboot, right? And from there you can never get it to go to fastboot USB?
Sent from my EVO using Tapatalk
If you're on the old partition layout have you followed my guide that I posted previously and tried to install MeanBean ROM?
Sent from my HTC device
CornDogg said:
From the main bootloader screen, you're pressing the power button on fastboot to go into fastboot, right? And from there you can never get it to go to fastboot USB?
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Yes, that was the case.
HOWEVER, I screwed up again. I reinstalled Ubunto on my laptop and now fastboot usb works just fine.
Sometimes it hurts to live. Now I just need to find out how to flash with fastboot on ubuntu.
windowpuncher said:
Yes, that was the case.
HOWEVER, I screwed up again. I reinstalled Ubunto on my laptop and now fastboot usb works just fine.
Sometimes it hurts to live. Now I just need to find out how to flash with fastboot on ubuntu.
Click to expand...
Click to collapse
Progress.
To get the fastboot binaries on Ubuntu, you can either download and install the Android SDK and install the platform tools or go download DirtyRacun from unlimited.io. The binaries are included in the .tar archive. You may need to use the chmod command on the fastboot and adb binaries to add permissions to execute the binaries.
Once you have the binaries executable, the commands are the same, except you'll have to elevate with sudo. So, assuming you're working in the directory where you have the fastboot executable and the boot.img file, the commands would be:
sudo ./fastboot devices
sudo ./fastboot flash boot boot.img
CornDogg said:
Progress.
To get the fastboot binaries on Ubuntu, you can either download and install the Android SDK and install the platform tools or go download DirtyRacun from unlimited.io. The binaries are included in the .tar archive. You may need to use the chmod command on the fastboot and adb binaries to add permissions to execute the binaries.
Once you have the binaries executable, the commands are the same, except you'll have to elevate with sudo. So, assuming you're working in the directory where you have the fastboot executable and the boot.img file, the commands would be:
sudo ./fastboot devices
sudo ./fastboot flash boot boot.img
Click to expand...
Click to collapse
fter I
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happens. My phone just sits there, the screen doesn't change, but it does say Fastboot USB. I restarted my phone but it got stuck at the dev boot screen with legal warnings in red text.
Addition: Booted to recovery to flash the ROM zip, not just the boot image, still restarts when attempting to install the Kernel.
The screen on your phone won't change when flashing the kernel with fastboot. After flashing it, press the power button on Fastboot to go back to the main bootloader screen and go to recovery to get into TWRP. From there, flash the .zip of the ROM that you pulled boot.img from like you normally would from TWRP (Install, select .zip, wipe cache/data, etc).
CornDogg said:
The screen on your phone won't change when flashing the kernel with fastboot. After flashing it, press the power button on Fastboot to go back to the main bootloader screen and go to recovery to get into TWRP. From there, flash the .zip of the ROM that you pulled boot.img from like you normally would from TWRP (Install, select .zip, wipe cache/data, etc).
Click to expand...
Click to collapse
I just did this, and the phone gets stuck at the dev boot screen that says HTC with the red legal text.
Have you tried a different ROM? Maybe try CM or Viper 4G. If you go the Viper 4G route, try this one: http://forum.xda-developers.com/showthread.php?t=2124391
I think the newest Viper 4G changes the partition layout or something, so I think that would just further complicate things at the moment.
CornDogg said:
Have you tried a different ROM? Maybe try CM or Viper 4G. If you go the Viper 4G route, try this one: http://forum.xda-developers.com/showthread.php?t=2124391
I think the newest Viper 4G changes the partition layout or something, so I think that would just further complicate things at the moment.
Click to expand...
Click to collapse
Yeah, I think I'll try cyanogenmod or stock android. Thank you for the suggestion, now i'll go see if it works.
No problem. If you decide to go the CM route, deck's CM11 is pretty great.
http://forum.xda-developers.com/showthread.php?t=2518211
Good luck!
CornDogg said:
No problem. If you decide to go the CM route, deck's CM11 is pretty great.
http://forum.xda-developers.com/showthread.php?t=2518211
Good luck!
Click to expand...
Click to collapse
I went on with installing DirtyRacun (http://unlimited.io/jewel.htm) and made it to step 12. As my phone ws rebooting it once again got stuck at that HTC red text dev warning screen. So now i'm stuck again.
windowpuncher said:
I went on with installing DirtyRacun (http://unlimited.io/jewel.htm) and made it to step 12. As my phone ws rebooting it once again got stuck at that HTC red text dev warning screen. So now i'm stuck again.
Click to expand...
Click to collapse
I didn't use DirtyRacun to S-OFF (I used RumRunner), so I can't speak on this with much authority. Just to confirm I understand correctly, though, you flashed the RUU (step 9), rebooted into the bootloader (step 10), and re-did the HTC Dev Unlock (step 11). Then, as it's booting up into the ROM installed via the RUU, it gets stuck?
Were you able to get anywhere with flashing Cyanogenmod? Or did you just decide to go through the S-OFF process instead?
Related
I can't install a rom, i get to the recovery menu choose what .zip to flash and i do a full wipe, then reboot to system all i',m stuck with is the htc screen anyhelp please nd thaknk you... I have no way to to use the phone it is without an ROM
EDIT: I am RELOCKED says on bootloader and i can't an ruu because it doesn't go thru for some reason, what can i do?
You have to follow the instructions for flashing kernels, which can be found in the dev section.
Flash cwm then try flashing a rom...
Sent from my PG86100 using xda premium
As previously stated, you can't flash kernels through recovery (the kernel is in the ROM) without going through fastboot first. Read the sticky in the dev section on flashing with hboot 1.5, its fairly simple. Happy flashing!
Sent from my PG86100 using xda premium
It just doesn't let me go past thru the htc whtie screen, i'm installing cm7 doesn't go past that screen.
If u don't get it fixed by tomorrow morning pm and I'll get u through it and running but I won't be free till about 8pm
Will do, thanks. i'm going to try to fix it tonight. Flash an RUU, at least and reroot it.
madplaya1 said:
Will do, thanks. i'm going to try to fix it tonight. Flash an RUU, at least and reroot it.
Click to expand...
Click to collapse
Try that and I promise u man I can get u flashing on 1.5 I do it all the time.
what I did was installed one of the ics roms then installed flash img gui and that should fix it. You can add more roms to the sd card just by booting into recovery and turning on usb toggle
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I followed the unroot your HTC unlocked evo guide, downloaded the RUU for the sprint evo 3d which I have, followed instruction and locked my phone again and now it just read the pg86img.zip, and i reboot it and it stays on the white HTC screen..... Please help thanks
Sent from my PG06100 using Tapatalk
RUU to stock
unlock with the HTCDEV method by following the steps here EXACTLY
http://forum.xda-developers.com/showthread.php?t=1239821
download Flash Image GUI from joeykrim (you can find links in apps forum or spend the .99 and buy it from the market)
put your desired ROM in the root of your SD card (using a file explorer or connect to your PC and enable USB)
run Flash Image GUI and point it to the ROM you want
Flash the image, it will tell you the file is too big and ask if you want it to index the file to find the kernel so accept that
when it's done reboot into recovery (you should have TWRP loaded now) and immediately flash the ROM you chose to pull the kernel from (wipe per instructions)
wait patiently, reboot, enjoy
I did it this way after moving from an OG EVO that was waaaay easier to root and flash, but once you've got it unlocked, using Flash Image is super easy to turn you into a flashaholic
good luck
Take the zip off card. I had this prob. Need to open cmd and push the img to card then send to fastboot then flash img thru cmd. Also have to use this method on any custom kernel rom to get it to get past white screen.
Sent from my PG86100 using xda premium
Problem is I can't access android. Im stuck on the bootloader screen or white HTC screen. PLUS, i relocked my phone using the command "oem lock" some thing like that.
Sent from my PG06100 using Tapatalk
madplaya1 said:
Problem is I can't access android. Im stuck on the bootloader screen or white HTC screen. PLUS, i relocked my phone using the command "oem lock" some thing like that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You should not have locked the phone madplaya.
Now follow the below steps:
Download any ROM or use any ROM that you have.
Download a superwipe tool ( not necessary if you want to manually wipe everything from recovery).
Download a custom recovery.IMG (cwm/twrp).
Now root ur phone
> open the ROM.zip (that you want to flash) and copy the boot.img from it to the fastboot folder , also copy the recovery.img to fastboot folder.
> open cmd prompt
> navigate to fastboot folder
> boot phone in bootloader
>select fastboot
> connect to PC (phone should say fastboot-usb)
> type command "fastboot flash boot boot.img"
> now type "fastboot boot recovery.img" (filename maybe different)
> Phone should boot into recovery ( make sure the red LED is lit up)
> now flash the superwipe tool.zip(or wipe everything manually if you dont have the tool)
> and then flash the same ROM from which you pulled the boot.img.......
Hope this helps...........
Quick question I'm gonna root this hboot 1.50 3vo this weekend and flash a Rom. Do I root fully then nandroid then full wipe and then flash Rom?
Sent from my PG86100 using Tapatalk
Nsandhu23 said:
Quick question I'm gonna root this hboot 1.50 3vo this weekend and flash a Rom. Do I root fully then nandroid then full wipe and then flash Rom?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you should follow the above steps by me after rooting your phone to flash a ROM...
mnomaanw said:
you should follow the above steps by me after rooting your phone to flash a ROM...
Click to expand...
Click to collapse
Okay thanks.!
Sent from my PG86100 using Tapatalk
mnomaanw said:
You should not have locked the phone madplaya.
Now follow the below steps:
Download any ROM or use any ROM that you have.
Download a superwipe tool ( not necessary if you want to manually wipe everything from recovery).
Download a custom recovery.IMG (cwm/twrp).
Now root ur phone
> open the ROM.zip (that you want to flash) and copy the boot.img from it to the fastboot folder , also copy the recovery.img to fastboot folder.
> open cmd prompt
> navigate to fastboot folder
> boot phone in bootloader
>select fastboot
> connect to PC (phone should say fastboot-usb)
> type command "fastboot flash boot boot.img"
> now type "fastboot boot recovery.img" (filename maybe different)
> Phone should boot into recovery ( make sure the red LED is lit up)
> now flash the superwipe tool.zip(or wipe everything manually if you dont have the tool)
> and then flash the same ROM from which you pulled the boot.img.......
Hope this helps...........
Click to expand...
Click to collapse
Tried this, got sent back to this bootloade screen man, thank anyways.
madplaya1 said:
Tried this, got sent back to this bootloade screen man, thank anyways.
Click to expand...
Click to collapse
Hey bro instead of all this writing and waiting pm me and I'll give u my number so we can do this over a phone.
Download the RUU.exe rom to your PC plug your phone in turn on fastboot and run the .exe on your PC...
Hey im new to all this but i wanted to have the pure Android on my one x+.
I have rooted the phone etc etc and i went to install this kernal and rom: http://forum.xda-developers.com/showthread.php?t=2057920
After the reboot it just gets stuck on a screen saying "INITIATING SWAGGER" as shown below. I have no idea what to do from here how to restore it or install a working rom?
Picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance for the help
Still not working, help please??? :/
LynchyY said:
Still not working, help please??? :/
Click to expand...
Click to collapse
You need to flash Gapps (20121212) as well.
Or you can wrote down your step, then more easier to known your problem.
xdacalvien said:
You need to flash Gapps (20121212) as well.
Or you can wrote down your step, then more easier to known your problem.
Click to expand...
Click to collapse
I am on the screen at the moment saying "Android is upgrading..." "Starting apps."
It has been on this screen now for about half an hour.
I have flashed gapps already although i may have done the wrong one but how can i get the one you just linked me onto my phone when its not even booting properly?
Thanks.
LynchyY said:
I am on the screen at the moment saying "Android is upgrading..." "Starting apps."
It has been on this screen now for about half an hour.
I have flashed gapps already although i may have done the wrong one but how can i get the one you just linked me onto my phone when its not even booting properly?
Thanks.
Click to expand...
Click to collapse
You need to go back the Recovery mode and flash the gapps..
Turn off your phone, Hold down the Volume Key (-) and press Power button to boot into bootloader.
This is quick step for you:
Installation:
install kernel
full wipe
flash rom
flash gapps
reboot into rom
[HOW TO] Unlock bootloader, Root, Flash Custom ROM, Flash Kernel
xdacalvien said:
You need to go back the Recovery mode and flash the gapps..
Turn off your phone, Hold down the Volume Key (-) and press Power button to boot into bootloader.
This is quick step for you:
Installation:
install kernel
full wipe
flash rom
flash gapps
reboot into rom
[HOW TO] Unlock bootloader, Root, Flash Custom ROM, Flash Kernel
Click to expand...
Click to collapse
Hey, thanks for the reply, can you give me a link to where i can find/download the kernel i need to flash?
Thanks
LynchyY said:
Hey, thanks for the reply, can you give me a link to where i can find/download the kernel i need to flash?
Thanks
Click to expand...
Click to collapse
Your need to go back ur ROM.zip file, and extract the boot.img. That is your boot.img... Any ROM got own boot.img.
So you not flash yet your BOOT.IMG.
xdacalvien said:
Your need to go back ur ROM.zip file, and extract the boot.img. That is your boot.img... Any ROM got own boot.img.
So you not flash yet your BOOT.IMG.
Click to expand...
Click to collapse
Yes but how do I install the kernel? what kernel do i install?
LynchyY said:
Yes but how do I install the kernel? what kernel do i install?
Click to expand...
Click to collapse
The Kernel here is means boot.img.
LynchyY said:
Yes but how do I install the kernel? what kernel do i install?
Click to expand...
Click to collapse
You'll need to open the zip file of the ROM you've flashed and find the boot.img contained within. Then use Hasoon's AIO Toolkit for HOX+ to flash the kernel (the bottom left option).
For some more information, the boot.img contains the kernel and the ramdisk for the device and is flashed to the boot partition of the device. Because the HOX+ is still S-OFF, we cannot flash the ROM and kernel together. We must flash the kernel (boot.img) separately using a utility called fastboot; the toolkit automates this process.
xdacalvien said:
The Kernel here is means boot.img.
Click to expand...
Click to collapse
Ok but how do i install the kernel if my pc is not even recognizing my phone?
Sorry for being a noob but i really don't want to break up my phone more than it already is.
Thanks.
LynchyY said:
Ok but how do i install the kernel if my pc is not even recognizing my phone?
Sorry for being a noob but i really dont want to **** up my phone more than it already is.
Thanks.
Click to expand...
Click to collapse
check the post #10, go to use the Hasson's AIO Kit to flash is more easier.
you need to install HTCDriver.exe from Hasson's AIO Kit.
xdacalvien said:
check the post #10, go to use the Hasson's AIO Kit to flash is more easier.
you need to install HTCDriver.exe from Hasson's AIO Kit.
Click to expand...
Click to collapse
I already have the HTCDriver.exe installed but my pc is not recognizing my phone because my phone don't boot.
LynchyY said:
I already have the HTCDriver.exe installed but my pc is not recognizing my phone because my phone don't boot.
Click to expand...
Click to collapse
Try to re-plug in the USB and test.
LynchyY said:
I already have the HTCDriver.exe installed but my pc is not recognizing my phone because my phone don't boot.
Click to expand...
Click to collapse
If the toolkit is not working, you'll need to do it manually I suppose.
1. Find the folder in the toolkit that contains fastboot.exe and navigate to that folder in a command prompt.
2. Hold the power and volume down buttons until your phone reboots into a white screen.
3. Connect it by USB if it isn't already and type "fastboot devices" and ensure that your device is listed (will just be a string of letters and numbers).
4. Once that works, type "fastboot flash boot path/to/boot.img" (I would recommend putting the boot.img in the same folder as fastboot.exe to make things easier on yourself).
5. If that command is executed successfully, run "fastboot reboot" if your device hasn't already rebooted.
xdacalvien said:
Try to re-plug in the USB and test.
Click to expand...
Click to collapse
Done that and nothing, my pc never recognizes the phone unless it is booted into android.At this point i can only get into the bootloader and recovery mode.
NasaGeek said:
If the toolkit is not working, you'll need to do it manually I suppose.
1. Find the folder in the toolkit that contains fastboot.exe and navigate to that folder in a command prompt.
2. Hold the power and volume down buttons until your phone reboots into a white screen.
3. Connect it by USB if it isn't already and type "fastboot devices" and ensure that your device is listed (will just be a string of letters and numbers).
4. Once that works, type "fastboot flash boot path/to/boot.img" (I would recommend putting the boot.img in the same folder as fastboot.exe to make things easier on yourself).
5. If that command is executed successfully, run "fastboot reboot" if your device hasn't already rebooted.
Click to expand...
Click to collapse
Thank you for this however i didnt work but maybe i did something wrong? Here is a SS of cmd after the process:
LynchyY said:
Thank you for this however i didnt work but maybe i did something wrong? Here is a SS of cmd after the process:
Click to expand...
Click to collapse
try" fastboot erase cache "
then " fastboot flash boot boot.img " again.
Remember, the boot.img is extract from the ROM.zip and put to the path same as fasboot.exe
LynchyY said:
Thank you for this however i didnt work but maybe i did something wrong? Here is a SS of cmd after the process:
Click to expand...
Click to collapse
ahh after this i tried again and the error was Low Battery so I will retry after charging my phone for a while.
Thanks again. I will let you know how it goes.
LynchyY said:
ahh after this i tried again and the error was Low Battery so I will retry after charging my phone for a while.
Thanks again. I will let you know how it goes.
Click to expand...
Click to collapse
After you haved success, you will become Member at this forum. FTW ~~~
How is now with your phone ?
My phone is rooted with the help of hasoons2000 toolkit, and it was done succesfully, but this morning, when i tried to flash a rom (cm 10.1) its now stuck on "initiating swagger" and i simply cant get past that
Need some help, ive rooted the right version of cwm recovery, cleared my download cache before the flash, and backed up my previously rom (stock)
What do i do!!?
Eddie5850 said:
My phone is rooted with the help of hasoons2000 toolkit, and it was done succesfully, but this morning, when i tried to flash a rom (cm 10.1) its now stuck on "initiating swagger" and i simply cant get past that
Need some help, ive rooted the right version of cwm recovery, cleared my download cache before the flash, and backed up my previously rom (stock)
What do i do!!?
Click to expand...
Click to collapse
Did you flash the boot.img?
gattzzz said:
Did you flash the boot.img?
Click to expand...
Click to collapse
No, i flashed the zip
I have acces to the bootloader menu now by the way
I'm pretty sure i need a RUU for my device now, but I don't know how to do that at the moment.
You have to go back to Fastboot, get the boot img, place it in your fastbood folder and navigate to ist.
then do the following
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
Then Reboot the device and it should be Start.
Cold Ice said:
You have to go back to Fastboot, get the boot img, place it in your fastbood folder and navigate to ist.
then do the following
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
Then Reboot the device and it should be Start.
Click to expand...
Click to collapse
How do i access the boot.img, when the file is in a zip? when i press it, it starts the rom, and gets stuck on "initiating swagger"
1. Download the ROM on to your PC.
2. Transfer a copy of the ROM Zip file to the phone.
3. On the PC, extract the ROM Zip file.
4. Open the extracted folder.
5. You will find the boot.IMG in the extracted folder. Using a toolkit or a command line, write the boot image to the phone while it is in bootloader mode.
6. Flash the ROM.
7. Flash any additional packages.
8. Reboot.
Edit: For adb sideload:
Follow steps 1, 3, 4, and 5, then sideload, then reboot
Sent from my One X+ using xda premium
Eddie5850 said:
How do i access the boot.img, when the file is in a zip? when i press it, it starts the rom, and gets stuck on "initiating swagger"
Click to expand...
Click to collapse
Open the .zip with 7zip or winrar and extract the boot.img or look in the rom thread if there is a downloadable boot.img, there's also a boot.img flasher around here in a toolkit. Don't know which one it is, didn't rooted/Unlocked yet.
Which ROM did you download?
The boot.img is either pointed out in the first post of the Custom ROM or it is in the download .zip
You need to copy the boot.img you find in the ADB/fastboot folder, then boot the X+ into the bootloader, select the fastboot option with the vol+/- and then connect the X+ with your computer.
I am not familiar with the all-in-one-toolkit but if I remember correctly you can flash it within the program.
The Insert Coin ROM and others have a kernel flasher. But I never used one of those either.
Look around a bit. Once the appropriate boot.img of the ROM you want has been flashed the ROMM will boot up.
sarcasticphoenix said:
1. Download the ROM on to your PC.
2. Transfer a copy of the ROM Zip file to the phone.
3. On the PC, extract the ROM Zip file.
4. Open the extracted folder.
5. You will find the boot.IMG in the extracted folder. Using a toolkit or a command line, write the boot image to the phone while it is in bootloader mode.
6. Flash the ROM.
7. Flash any additional packages.
8. Reboot.
Edit: For adb sideload:
Follow steps 1, 3, 4, and 5, then sideload, then reboot
Sent from my One X+ using xda premium
Click to expand...
Click to collapse
All right, since I have no access to the usb debugging, i tried to sideload the rom (Cm 10.1 4.2.2), but when i use the toolkit with the script cmd
It says this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried it again, and it says this:
Sorry if i am a complete noob here
Eddie5850 said:
All right, since I have no access to the usb debugging, i tried to sideload the rom (Cm 10.1 4.2.2), but when i use the toolkit with the script cmd
It says this:
Tried it again, and it says this:
Sorry if i am a complete noob here
Click to expand...
Click to collapse
adb kill server
fastboot flash boot boot.img
done. Quite honestly you should read up before flashing rom's ALL the info is in this forum.
Sorry if I'm thread jacking, but is there a way to flash a kernel from in the phone itself? my PC took a dump, it'll be a few weeks till i can afford to replace it.
Great news everyone!
I saved my phone, and its now working like stock normal
The problem was that i flashed an entire zip file instead of a boot.img file, causing my phone to bootloop, after countless tries to fix this, I decided to unroot the phone with fastboot, recovery and a RUU file.
My phone is now working, thanks for helping!
Until we get S-OFF, we can't flash kernels from the phone itself.
Sent from my One X+ using xda premium
So, sorry if i'm thread bumping, but if I want to give it a try again at flashing a rom, and try avoiding what happen last time
Are these the following step correct?
Do a backup of current rom in cwm recovery
Wipe data/factory reset 3 times in cwm recovery
Wipe cache partition in cwm recovery
Wipe dalvik cache cwm recovery
Flash the zip containing the cm10.1 zip
And can I do all this without the need of installing rom manager?
Don't forget that you need to flash the kernel separately. Because we don't have S-OFF on our device, we have to flash the kernel from a PC.
1. Extract boot.img (this is the kernel) from the ROM zip file
2. Open a cmd prompt and cd to the directory containing the extracted boot.img
3. Connect your device and reboot it to the bootloader with the command:
adb reboot bootloader
4. Flash the kernel with the commands:
fastboot flash boot boot.img
fastboot erase cache
5. Reboot your device with:
fastboot reboot
You can do these steps before or after flashing the ROM but remember that you should have the android SDK platform-tools folder in your PATH before it'll work (assuming you use windows).
Sent from my cellular telephone using xda premium
o_O said:
Don't forget that you need to flash the kernel separately. Because we don't have S-OFF on our device, we have to flash the kernel from a PC.
1. Extract boot.img (this is the kernel) from the ROM zip file
2. Open a cmd prompt and cd to the directory containing the extracted boot.img
3. Connect your device and reboot it to the bootloader with the command:
adb reboot bootloader
4. Flash the kernel with the commands:
fastboot flash boot boot.img
fastboot erase cache
5. Reboot your device with:
fastboot reboot
You can do these steps before or after flashing the ROM but remember that you should have the android SDK platform-tools folder in your PATH before it'll work (assuming you use windows).
Sent from my cellular telephone using xda premium
Click to expand...
Click to collapse
Can't I just use the toolkit for my hox+? Hasoon2000 says you can just flash a kernel? I could be wrong though.
I believe you can, and that the way I described above is actually the way Hassoon's toolkit does the job. Just make sure the boot image is named correctly for the toolkit to pick it up, and make sure you put it in the correct folder (from memory, it's the "kernels" folder).
I use Linux, so Windows users feel free to correct me if I made any mistakes.
Sent from my cellular telephone using xda premium
Dell has updated their open source site with the developer files for the Lollipop update for the Venue 8 7840:
http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
This includes the kernel source, a guide Doc, and a "blankphone" image which will re-partition the device and leave it in the fastboot interface OS and wait for a system image to be flashed. It does not erase or provision a system image or boot image. The documentation mentions a separate "fastboot" image paired with the "blankphone" image, and traditionally (based on files posted by other OEMs) the "fastboot" zip is what contains the OS images. So hopefully (maybe?) they will be posting that at some point. We should be able to get images pulled off working devices for people to flash.
This "blankphone" zip should function as an "unbrick" and put a mis-flashed device back into a functioning (flashable) state, but you may end up without an OS. (This is why I called it "partial" unbrick, because you won't have a brick but you won't necessarily have a booting-to-Android device either.)
ALSO A WARNING: This should be all fine and good but proceed with caution.
I have flashed the IFWI-only.xml and successfully booted back to Android.
The zip file can be flashed with Phone Flash Tool Lite, available here from Intel for Windows and Linux.
There is a "Flash file" selector in Phone Flash Tool.
To unbrick and format, use the file: flash-DDO_BB.xml
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To just flash the unlocked bootloader firmware, use the file: flash-IFWI-only.xml
DO NOT use the EraseFactory xml; I'm not certain but I think there are DRM keys in the /factory partition, and you could permanently break things like Netflix if you erase it.
Since mine is currently useless, I may as well try this. Will the image you uploaded here work?
Don't have access to the tablet at the moment but I'll try when I get in (couple of hours).
I know @wirebook tried on the older bootloader and failed but not harm in trying with this new stuff I suppose...
That system.img doesn't flash I think... Though it sounds like it's just an issue of repacking it somehow.
This is great news!
If bootloader can be unlocked, does it mean someday (if best) it is possible to install windows os on this little pad?
wonglynn2004 said:
This is great news!
If bootloader can be unlocked, does it mean someday (if best) it is possible to install windows os on this little pad?
Click to expand...
Click to collapse
Windows is unlikely, as it would require additional drivers and a custom bootloader OS to be created, among other issues. Linux may be possible though.
I've managed to unbrick my device, but I'm honestly not sure how.
So using the intel flash tool, I used the option flash-DDO_BB.xml, understanding that it would wipe the device (erase system, repartion, etc). I then had access to fastboot. From fastboot I attempted to flash the system.img @xBIGREDDx uploaded, obviously that failed with the sparse image header issue.
Next I converted the system.dat.new in the OTA to a system.img, attempted to flash that from fastboot, no go.
I decided it might be a good idea to flash the boot.img from the OTA, so I did that. Ended up on the original Dell/Intel boot animation (progress?). This seemed to infinitely bootloop (however maybe I was just impatient?).
I then booted CWM using the temp. recovery method (T4), wasn't able to do much at all, most directories were empty and nothing was mountable. Rebooted the tablet once more, went to get a drink and it's booted into Lollipop!?
I'm both confused and pleased... Can anyone shed any light?
anggusss said:
I'm both confused and pleased... Can anyone shed any light?
Click to expand...
Click to collapse
Hahaha not sure, maybe the reboot caused it to process the update again? The OTA may have been in the cache still.
Update: I have looked at the xml files and it turns out they are not erasing the boot or system partitions after all. That has been the standard procedure in the past so I didn't think to check. They are, however, wiping the data partition, and they wipe the cache twice. Maybe they've been reading XDA too much?
Ah I see. So if my system was never wiped, I assume flashing the new boot.img from fastboot is what kicked it into life.
I probably should have posted somewhere that I wrote a second query to Dell and heard back from someone in Legal six days ago stating that they were going to go bug the team and get the images posted online. They promised to follow up- never did- but looks like the rest of you were a lot more diligent in checking out the open source repository.
Anyway, the tablet I was working on belonged to a family member now living in a different city. Seems like we've figured out more or less how to unbrick this thing, so that's fantastic! I'm a bit confused as to which guide / instructions I should be passing along to convert the "it's-okay-it-makes-a-pretty-doorstop" back to working condition? Much appreciated!
For now, I wanna ask how to unroot the device with 5.0.2 if an OTA out there that I'm gonna update but don't wanna brick my device?
wonglynn2004 said:
For now, I wanna ask how to unroot the device with 5.0.2 if an OTA out there that I'm gonna update but don't wanna brick my device?
Click to expand...
Click to collapse
Wait for someone else to confirm, but I don't think it was the rooting that caused the OTA to fail, it was the developer unlock. I imagine you're safe to OTA with root applied although someone correct me if I'm wrong.
anggusss said:
Wait for someone else to confirm, but I don't think it was the rooting that caused the OTA to fail, it was the developer unlock. I imagine you're safe to OTA with root applied although someone correct me if I'm wrong.
Click to expand...
Click to collapse
Yes, it was the developer unlock firmware that broke the OTA, not rooting. With the new Lollipop boot firmware, I think even if it's the unlocked firmware we should be good moving forward.
If you still want to unroot, there should be a menu option in SuperSU, it's like "cleanup" or something.
wirebook said:
I'm a bit confused as to which guide / instructions I should be passing along to convert the "it's-okay-it-makes-a-pretty-doorstop" back to working condition? Much appreciated!
Click to expand...
Click to collapse
1) Install Phone Flash Tool Lite from Intel.
2) Download the blankphone zip from Dell's open source site.
3) Load the zip file with Phone Flash Tool and select "Flash file: flash-DDO_BB.xml"
4) Boot the tablet with the Volume Up button held for about 10 seconds. You won't see anything on the display.
5) Connect USB to the computer. Phone Flash Tool should recognize the device and list the "Status:" as "FW_DNX" mode. If not, try powering off the tablet by holding the power button for ~12 seconds, and then try booting again with the Volume Up key held. Eventually you'll get the right mode.
6) Click "Start to flash" and wait.
7) Even after it hits 100% in the Flash Tool, maybe wait another 5 minutes or so, just in case.
If all goes well you'll end up in the fastboot OS. If all goes really well, you'll end up with a functioning Android device.
xBIGREDDx said:
1) Install Phone Flash Tool Lite from Intel.
2) Download the blankphone zip from Dell's open source site.
3) Load the zip file with Phone Flash Tool and select "Flash file: flash-DDO_BB.xml"
4) Boot the tablet with the Volume Up button held for about 10 seconds. You won't see anything on the display.
5) Connect USB to the computer. Phone Flash Tool should recognize the device and list the "Status:" as "FW_DNX" mode. If not, try powering off the tablet by holding the power button for ~12 seconds, and then try booting again with the Volume Up key held. Eventually you'll get the right mode.
6) Click "Start to flash" and wait.
7) Even after it hits 100% in the Flash Tool, maybe wait another 5 minutes or so, just in case.
If all goes well you'll end up in the fastboot OS. If all goes really well, you'll end up with a functioning Android device.
Click to expand...
Click to collapse
Thank you so much for posting that! I'll attempt to walk my father through the process this weekend.
Stuff wasn't quite working right for me, the screen was turning on randomly, reboots took a ridiculously long time, and a few other things. Decided that it may be better to start with a fresh system partition.
Tried converting both the system.img from @xBIGREDDx and the one from the lollipop OTA to sparse imgs and flashing, however I'm getting
FAILED (remote: flash_cmds error!
When I try to flash system, during the write stage. I'd like to think they're correct sparse images since fastboot reads and sends them to the device.
If I look at the tablet screen during the flash, it complains of an "Unknown chunk type" before failing.
I can get to the default recovery and fastboot, I just don't seem to be able to flash something to my now empty system partition from fastboot...
EDIT: Managed to flash system through the tethered recovery, but I'm still met with a black screen on regular boot.
EDIT2: Fixed, had to push xBIGREDDx's system.img to the device over adb and then dd it to the system partition. The advantage of using that is that it's pre-rooted! I guess we just can't flash system through fastboot.
Another note, I wasn't able to ever get the tablet booting straight into fastboot mode using power/volume buttons. I had to keep sticking it into DnX mode and then using a cut-down xml config along with the flash tool lite to get it to fastboot.
anggusss said:
EDIT2: Fixed, had to push xBIGREDDx's system.img to the device over adb and then dd it to the system partition. The advantage of using that is that it's pre-rooted! I guess we just can't flash system through fastboot.
Click to expand...
Click to collapse
Can you explain how you did this? Through the tethered recovery or through fastboot or....? Trying to walk someone through this via Skype turns out to be a lot harder than I expected...
wirebook said:
Can you explain how you did this? Through the tethered recovery or through fastboot or....? Trying to walk someone through this via Skype turns out to be a lot harder than I expected...
Click to expand...
Click to collapse
Sorry, I could have been clearer.
The steps I performed:
First, booted to fastboot
Trigger the tethered recovery (T4)
Once in the recovery, I then formatted /system using the graphical menu. (Probably not necessary since we're DDing the img directly?)
I had a microsd card in the device which was EXT4 formatted, so I pushed the system.img to that after mounting it by hand.
Code:
mount -t ext4 /external_sd /dev/block/mmcblk1p1
Then from the PC side
Code:
adb push system /external_sd/system.img
You could probably push to the data partition if you can get it mounted in the event you don't have a microsd.
Once you have the system.img on the device, you can dd it onto the system partition
Make sure /system is unmounted
Code:
umount /system
dd if=/external_sd/system.img of=/dev/block/by-name/system
NOTE: /dev/block/by-name/system may be wrong, I'm going from memory. I'll correct it when I get in from work.
After flashing system, reboot to fastboot again
Code:
adb reboot fastboot
And finally flash the boot.img from the OTA zip I uploaded
Code:
fastboot flash boot boot.img
Perform a normal boot, and it should be working. First boot takes a while, 3-4 minutes.
anggusss said:
Another note, I wasn't able to ever get the tablet booting straight into fastboot mode using power/volume buttons. I had to keep sticking it into DnX mode and then using a cut-down xml config along with the flash tool lite to get it to fastboot.
Click to expand...
Click to collapse
It's possible your fastboot partition is broken. After using the Flash Tool to get into fastboot, you could try:
fastboot flash fastboot droidboot.img
There is a droidboot.img in the update.zip from the OTA.
xBIGREDDx said:
It's possible your fastboot partition is broken. After using the Flash Tool to get into fastboot, you could try:
fastboot flash fastboot droidboot.img
There is a droidboot.img in the update.zip from the OTA.
Click to expand...
Click to collapse
I did try that quite a few times but no luck. I just seem completely unable to boot straight into fastboot. I either have to reboot to it using ADB or use the flashtool. Not necessarily a problem, just an inconvenience.
Will there be a TWRP version compatible with oxygen os V14 currently running on European Nord 2?
I tried previous TWRP guides for the Nord 2 but it didn't work.
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Zombnombs said:
Recovery OS's like TWRP works with all versions of the nord2 regardless of the update version.
More than likely you didn't follow all steps correctly. There are multiple mistakes you can make which results in the stock recovery OS being reflashed and the TWRP recovery being overwritten; I'm not completely sure of all the scenarios in which this happens, but you definitely made a miss-step somewhere.
I'm also running an EU nord variant with V14 and TWRP works fine, I've just noticed that after a few reboots TWRP partition gets overwritten by the stock OS again, in which case I just simply reflash the TWRP if i need to use it.
Click to expand...
Click to collapse
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Copaxy97 said:
oh..ok i didn't know this. Thanls for the information
I actually followed the steps.
fastboot devices -> then flash the vbmeta -> then flash TWRP -> but then i cannot switch to the Recovery anymore.
Booting the phone works fine but i cannot access the recovery anymore and it always directly jumps me back to fastboot mode. I followed several videos and tutorials here but whatever i do what works for others seems to not work for me
Whenever i try it seems like the recovery is gone. Even stock recovery is not accessable anymore. I wonder what i did wrong or if i need to flash other files too.
Click to expand...
Click to collapse
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Zombnombs said:
Assuming you've already unlocked bootloader and have all the mediatek drivers and ADB tools installed on your computer; Simply retry flashing vbmeta with the disable verity flag, then reflash twrp, and then reboot into recovery.
Make sure you've got a copy of the vbmeta.img and TWRP.img downloaded and place them in your ADB platform tools folder. Then run these commands
Make sure you shift-right click (for windows) on empty space in your platform tools folder and open powershel or command prompt (this is important), then send the following commands
Code:
fastboot devices
and wait for a response from your device to ensure it's connected
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
Code:
fastboot flash recovery [YourTWRPfileName]
eg my twrp file name is TWRPopn2.img so i type "fastboot flash recovery twrpopn2.img"
then
Code:
fastboot reboot recovery
Make sure your ADB terminal and phone both say the flash was succesful after each flash. If not, then you likely didn't flash the partition at all.
My guess is likely that you shift-right clicked to open the powershell window in the wrong folder, such as your desktop, in which case sending the flash commands cann't find the right file to flash? Just a theory. Definitely sounds like your recovery partition got wiped though. You could also try redownloading TWRP to make sure you're using the right version of it.
Click to expand...
Click to collapse
Thanks for your help. I will try that again later.
What i can say i 100% opened the command prompt in the correct folder and the flash always said succesful.
I also thought about the command promt folder error before but it is correct. At least somehting got wiped (my recovery) but i simply cannot access it.
I will try again later and go over each step step by step and share ym results here. I hope i did a mistake because otherwise i don't know how to locate the problem.
Okey i did it again like the tutorial and also a second time like you said but it sadly didn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my output from the command line. i use minimal ADB and fasstboot. But normal powershell by shift right click gives me the same output.
But when i try to reboot and boot into the recovery it just jumps to fastboot mode. So the stock recovery got flashed or removed then. But why i cannot boot into twrp?
Bootloader unlocked and based on the messages in the cmd everything fine.
Any ideas?
***Edit***
It worked now. If you ask me why, i don't know.
I did exactly the same in minimal adb and fastboot tools and on powershell. Both didn't work.
I did it in total 5 times and the last one in powershell randomly was succesful lol.
weird...
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Zombnombs said:
looks like the issue is more likely to do with your method of rebooting into recovery, as your reboot command did not seem to work.
Could be an issue with MinimalADB, or many other factors. If you're using the power button and volume keys combination, make sure you do it with your phone unplugged, as with the phone plugged in the combination boots to fastboot instead of recovery.
Click to expand...
Click to collapse
Yeah might be true. I don't know.