Related
As the title says i can't flash any boot images
expect swiftdroids boot .img
Everytime i go onto recovery the swiftdroid boot image
comes up for about 1 sec and then the recovery menu
comes up!!!
I also tried flashing different CWMs but the same!!
My normal boot image does come up if i don't go to
recovery!! (It is the android boot image)
Cause of this i can't flash any type of boot .img
expect the swiftdroid's boot .img
Anyone know how i can get rid of this??
I am using SuperFast Froyo so its got nothing to do
with swiftdroid!!
I did go to data/local/
but nothings there so i went into data/local/tmp
and nothings there too. (used root explorer)
Any help will be appreciated!!
Thank you!!
androidboss7 said:
As the title says i can't flash any boot images
expect swiftdroids boot .img
Everytime i go onto recovery the swiftdroid boot image
comes up for about 1 sec and then the recovery menu
comes up!!!
My normal boot image does come up if i don't go to
recovery!! (It is the android boot image)
Cause of this i can't flash any type of boot .img
expect the swiftdroid's boot .img
Anyone know how i can get rid of this??
I also tried flashing different CWMs but all the same results!!!
I am using SuperFast Froyo so its got nothing to do
with swiftdroid!!
I did go to data/local/
but nothings there so i went into data/local/tmp
and nothings there too. (used root explorer)
Any help will be appreciated!!
Thank you!!
Click to expand...
Click to collapse
I'm guessing you've already done a wipe & flash lol.
What do you mean by "...i can't flash any boot images...". Won't you be able to do that via fastboot or recovery? On my device with Swiftdroid, when I enter recovery it also comes up with the Swiftdroid logo and then quickly to recovery (when I decide to boot to recovery). Are you trying to say that the Swiftdroid logo comes with other ROMs instead of Swiftdroid itself?
jhonnyx1000 said:
I'm guessing you've already done a wipe & flash lol.
What do you mean by "...i can't flash any boot images...". Won't you be able to do that via fastboot or recovery? On my device with Swiftdroid, when I enter recovery it also comes up with the Swiftdroid logo and then quickly to recovery (when I decide to boot to recovery). Are you trying to say that the Swiftdroid logo comes with other ROMs instead of Swiftdroid itself?
Click to expand...
Click to collapse
Yes I did try wiping everything!
I use SuperFast Froyo!!
And still swiftdroids boot image
Comes up when i boot into recovery!!!
And I mean i can't flash via
Recovery!!
But I can with fastboot!
But I want to flash with recovery
Cause some roms can only
flashes with recovery
Sent from my GT540 using Tapatalk
androidboss7 said:
Yes I did try wiping everything!
I use SuperFast Froyo!!
And still swiftdroids boot image
Comes up when i boot into recovery!!!
And I mean i can't flash via
Recovery!!
But I can with fastboot!
But I want to flash with recovery
Cause some roms can only
flashes with recovery
Sent from my GT540 using Tapatalk
Click to expand...
Click to collapse
It could be a problem with the recovery image. Do you get the Swiftdroid logo when booting normally?
jhonnyx1000 said:
It could be a problem with the recovery image. Do you get the Swiftdroid logo when booting normally?
Click to expand...
Click to collapse
No!!
That's the weird thing!!
I can only flash updates zips
But it still says error flashing boot
Image!!!
But I can't flash any boot image
Expect the swiftdroids!!
Do u know why this happens??
Sent from my GT540 using Tapatalk
androidboss7 said:
No!!
That's the weird thing!!
I can only flash updates zips
But it still says error flashing boot
Image!!!
But I can't flash any boot image
Expect the swiftdroids!!
Do u know why this happens??
Sent from my GT540 using Tapatalk
Click to expand...
Click to collapse
Maybe the other ROMs take more space than Swiftdroid's boot image. How big are the other's ROMs' boot images compard to Swiftdroid boot images?
jhonnyx1000 said:
Maybe the other ROMs take more space than Swiftdroid's boot image. How big are the other's ROMs' boot images compard to Swiftdroid boot images?
Click to expand...
Click to collapse
Don't know!!
But I think if I delete that boot img
Of the swiftdroids one it might
Solve the problem!!
Edit: ok right now I reflashed
recovery with boot animation disabled!!
And the swiftdroid didn't come up!!
then i tried with boot animation abled
and it still didn't come up!! YAA
But to confirm i am gonna flash a new new rom
to see if it has the same problem!!
Sent from my GT540 using Tapatalk
Just waiting for the Froyo Optimum!!
Edit: No i still can't flash any boot img's!!!
anyone know how i can restart my whole phone
so its got nothing on it???
or perhaps an answer to this problem???
Nupe still can't flash boot .img
Sent from my GT540 using Tapatalk
Anyone ?????
Sent from my GT540 using Tapatalk
By any chance do you have ClockworkMod Recovery on your phone???
Because with this one you can try to access it and over there Wipe Dalvik Cache, do a wipe data/factory reset, and if this doesn't works to wipe cache partition.
After doing this I will look for a restore image over the web, there are tons of them, Install one of them with the ClockworkMod Recovery, and just after the first boot access once again the Recovery and do a wipe data/factory reset. I think this way you will have a phone with nothing on it just a new OS.
If you need a guide for installing ClockworkMod this is the first one I used:
http://forum.xda-developers.com/showthread.php?t=1224747
And thanks to effortless. for this awesome guide.
Hope it works...
suzukah said:
By any chance do you have ClockworkMod Recovery on your phone???
Because with this one you can try to access it and over there Wipe Dalvik Cache, do a wipe data/factory reset, and if this doesn't works to wipe cache partition.
After doing this I will look for a restore image over the web, there are tons of them, Install one of them with the ClockworkMod Recovery, and just after the first boot access once again the Recovery and do a wipe data/factory reset. I think this way you will have a phone with nothing on it just a new OS.
If you need a guide for installing ClockworkMod this is the first one I used:
http://forum.xda-developers.com/showthread.php?t=1224747
And thanks to effortless. for this awesome guide.
Hope it works...
Click to expand...
Click to collapse
Yes i do have clockwordmod and yes
i did try factory reset through clockwordmod
but still the same problem...
And did you tried the rest of the things I told you?? To wipe the Dalvic cache and to use another restore image??
suzukah said:
And did you tried the rest of the things I told you?? To wipe the Dalvic cache and to use another restore image??
Click to expand...
Click to collapse
Yup
I tried basically everything ..
Sent from my GT540 using Tapatalk
Here is what I have done so far:
Unlocked bootloader from HTC DEV
Flashed custom recovery
I can get into the recovery fine, and have flashed a custom ROM but I am getting stuck at the white HTC boot screen
Can anyone offer some guidance please?
How long does it stick at the white HTC logo? did it write "quietly brilliant" or not? It can take a long time to boot up a new ROM, but if it's longer than 10 minutes then pull the battery and try flashing the ROM again.
check the MD5 sum of the ROM on the SDcard, and the MD5 the dev published. If they're different, re-download the ROM.
Not unheard of for a ROM with a good MD5 to flash badly, happened to me when I flashed recovery to a Sensation last week. Simply re-flashing it sorted it out OK.
chrisund123 said:
How long does it stick at the white HTC logo? did it write "quietly brilliant" or not? It can take a long time to boot up a new ROM, but if it's longer than 10 minutes then pull the battery and try flashing the ROM again.
check the MD5 sum of the ROM on the SDcard, and the MD5 the dev published. If they're different, re-download the ROM.
Not unheard of for a ROM with a good MD5 to flash badly, happened to me when I flashed recovery to a Sensation last week. Simply re-flashing it sorted it out OK.
Click to expand...
Click to collapse
thanks for the reply buddy
no it does not say quietly brilliant, i've flashed a few ROMS all exhibiting the same behaviour.
Can you confirm that the steps I have taken are correct? One obvious thing that I think I am missing is actually rooting the phone? Yes I have unlocked the bootloader and installed a custom recovery, but how do I root? Sorry to sound like a noob, I am a Samsung man, just temporarily using this phone.
winwiz said:
thanks for the reply buddy
no it does not say quietly brilliant, i've flashed a few ROMS all exhibiting the same behaviour.
Can you confirm that the steps I have taken are correct? One obvious thing that I think I am missing is actually rooting the phone? Yes I have unlocked the bootloader and installed a custom recovery, but how do I root? Sorry to sound like a noob, I am a Samsung man, just temporarily using this phone.
Click to expand...
Click to collapse
It sounds like you're doing it right, what version of recovery are you using? clockwork?
Basically, the steps are:
1.Boot into recovery
2.choose "Wipe data/factory reset", confirm, and go back to main menu
3.Select "Install zip from SDcard", select "choose zip from SDcard", and then select the ROM. Confirm, and then let it do it's thing. Then go back and choose to reset the phone, and you should be away (after a few minutes for it to boot up).
chrisund123 said:
It sounds like you're doing it right, what version of recovery are you using? clockwork?
Basically, the steps are:
1.Boot into recovery
2.choose "Wipe data/factory reset", confirm, and go back to main menu
3.Select "Install zip from SDcard", select "choose zip from SDcard", and then select the ROM. Confirm, and then let it do it's thing. Then go back and choose to reset the phone, and you should be away (after a few minutes for it to boot up).
Click to expand...
Click to collapse
yeah clockwork
exactly the process I have followed
will try again
winwiz said:
yeah clockwork
exactly the process I have followed
will try again
Click to expand...
Click to collapse
Use EXT4 recovery. Alot of DHD/Inspire roms do not like or use Clockwork mod recovery due to it causing issues.
To add what zel recommended, the reason its failing to boot is because you unlocked via HTC dev. With this method the boot.img has to be flashed seperately, via fast boot with the command fastboot flash boot boot.img(done using sdk). 4ext recovery has implemented a nice feature of being able to flash the bootimg for son/HTC dev unlocked devices.
Sent from my Inspire 4G using XDA
You should try using AHK (Advanced Hack Kit). It is really easy to use tool, you just need to install the drivers provided with it.
I was use a nexus4tookit v1.3.0 to root my nexus 4 , however I was download a Liquidsmooth and install from sdcard , but now the mobile cannot open , just load in liquid-smooth logo screen, what can I do now? My nexus 4 is JOP40D , Thanks a lot.
You may have a bad download. Check the md5 sum or re download it and try flashing it again.
Sent from my Nexus 4 using Tapatalk 2
Restore the backup you should have made in recovery before you flashed anything.
Hold down power for ten seconds to reboot, then hold volume down to enter boot loader. You can get to recovery from there.
First off. You shouldn't be using a toolkit, they get you from Point A to Point B. But now you are trying to backtrack because your phone won't boot. This is why people shouldn't use toolkits, you are getting to Point B without knowing what you're doing.
Is it stuck at the bootanimation screen? Did you wipe factory settings when flashing the ROM?
estallings15 said:
Restore the backup you should have made in recovery before you flashed anything.
Hold down power for ten seconds to reboot, then hold volume down to enter boot loader. You can get to recovery from there.
Click to expand...
Click to collapse
I already unlock the bootloader ， but I can't enter to boot loader now , just can enter to recovery mode or restart boot loader ,power off or start.:crying:
cf017 said:
I already unlock the bootloader ， but I can't enter to boot loader now , just can enter to recovery mode or restart boot loader ,power off or start.:crying:
Click to expand...
Click to collapse
If you can get into recovery, you're fine. Is this your first Android phone? Your first step after rooting is always to make a backup.
Anyway, flash Franco's kernel. It plays well with liquid smooth. That should fix you up. You will figure out how if you STOP PANICKING and try.
estallings15 said:
If you can get into recovery, you're fine. Is this your first Android phone? Your first step after rooting is always to make a backup.
Anyway, flash Franco's kernel. It plays well with liquid smooth. That should fix you up. You will figure out how if you STOP PANICKING and try.
Click to expand...
Click to collapse
and not use toolkits! take the 15-25 minutes to read whats going on and not click one button to do it all for you
that's why OP is panicing because he didnt manually do it, a toolkit did it for him.
Post sent in error apologies
bash156 said:
Hi I hope you don't mind me messaging you I just noticed your last post that we should use toolkits for our phone can you please tell me what is the best way to do it I apologise for asking this is my first android phone and I'm realising that battery life is crap and I've been reading about people making changes to make their battery life live longer
Regards
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
We should use toolkits? I never said a thing about using them. The best way is to NOT use them. If this is your first android phone, it is IMPERATIVE to know simple ADB and Fastboot methods so you won't fall into the common errors when people use toolkits getting them into things they don't understand.
http://forum.xda-developers.com/showthread.php?t=1972508 is a guide to get started after you boot up, you can then proceed to go into the Original and Android dev forums to select your ROM / Kernel that you desire. I'd recommend CM10.1 (jellybro) + Franco Kernel R20. --- so after unlocking bootloader. Put the ROM, Gapps, Kernel on your phone storage using USB cable.
Use computer --- ADB... "adb reboot bootloader"
fastboot flash recovery <nameofrecovery>.img (download TWRP or CWR and put it in same folder as fastboot /platform-tools/ most likely)
boot into recovery (use volume up/down to navigate then power to enter)
wipe factory settings,dalvik,cache
flash rom then gapps then kernel (gapps and kernel can be reversed up to you)
then reboot.
done.
Apologies I meant that we should not be using tool kits my bad
Sent from my Nexus 4 using xda app-developers app
bash156 said:
Apologies I meant that we should not be using tool kits my bad
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
He answered your question with great detail. Hit the thanks button.
bash156 said:
Apologies I meant that we should not be using tool kits my bad
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No problem. Just read what I said above, if u have any questions, feel free to ask. It's a very straight forward guide on how to unlock your bootloader. The stuff thats not included in there would be:
- Download ROM, Gapps (optional depending what rom you use. the rom says whether its included or not, if it doesnt say assume its in there), kernel (optional but recommended u switch --- upon flashing a new version u will need to reflash the kernel)
- Flashing Custom Recovery while in Bootloader Mode (which I said in my post on how to do.. basically download TWRP or CWR [you choose, i recommend twrp] and put the .img folder in the same folder as fastboot.exe)
- Use vol up / down to go to recovery in bootloader mode (it says the text on the phone)
- Wipe factory
- Flash ROM, Gapps, Kernel (gapps and kernel order doesnt matter. ROM goes first)
- Reboot to system
..... done.
edit: yeah what estallings said thanks given.
Thank you very much for your help I'm going to try and unlock the bootloader now I'll let you know how I get on to back everything that's on my phone already can I just sync to my Google account
Sent from my Nexus 4 using xda app-developers app
sorry to bother you again thanks to you I have now unlocked bootloader but im finding it confusing on what to do next I havent managed to find the cm 10.1 and franco kernal you talked about is there a link somewhere for them
bash156 said:
sorry to bother you again thanks to you I have now unlocked bootloader but im finding it confusing on what to do next I havent managed to find the cm 10.1 and franco kernal you talked about is there a link somewhere for them
Click to expand...
Click to collapse
Original development.
bash156 said:
sorry to bother you again thanks to you I have now unlocked bootloader but im finding it confusing on what to do next I havent managed to find the cm 10.1 and franco kernal you talked about is there a link somewhere for them
Click to expand...
Click to collapse
CM10.1 Jellybro: http://forum.xda-developers.com/showthread.php?goto=newpost&t=2015081
Franco Kernel: http://forum.xda-developers.com/showthread.php?t=2002782
Download CM10.1 Jellybro + Gapps + Kernel R20.
zephiK said:
CM10.1 Jellybro: http://forum.xda-developers.com/showthread.php?goto=newpost&t=2015081
Franco Kernel: http://forum.xda-developers.com/showthread.php?t=2002782
Download CM10.1 Jellybro + Gapps + Kernel R20.
Click to expand...
Click to collapse
Hi I did everything you said I flashed the cm10 gapps and kernel now its stuck on the cynogenmod logo I went back to recovery wiped everything and tried to flash cm10 and the rest again and still stuck on the cynogen mod logo have I done something wrong because I dont have anything backed up
bash156 said:
Hi I did everything you said I flashed the cm10 gapps and kernel now its stuck on the cynogenmod logo I went back to recovery wiped everything and tried to flash cm10 and the rest again and still stuck on the cynogen mod logo have I done something wrong because I dont have anything backed up
Click to expand...
Click to collapse
When you mean wipe everything... just factory settings, dalvik, cache right?
- Wipe Factory, Dalvik, Cache
- Flash CM10
- Flash Gapps
- Flash Kernel
- Reboot.
zephiK said:
When you mean wipe everything... just factory settings, dalvik, cache right?
- Wipe Factory, Dalvik, Cache
- Flash CM10
- Flash Gapps
- Flash Kernel
- Reboot.
Click to expand...
Click to collapse
I always wipe system as well. I used to not do that, but I found less phantom issues appeared if I wiped system.
estallings15 said:
I always wipe system as well. I used to not do that, but I found less phantom issues appeared if I wiped system.
Click to expand...
Click to collapse
Interesting. First time I've heard this, I will have to try that sometime although for the last year I've been pretty content with CM + Franco set up. Maybe when a new version of Android comes out, I swap over to that AOSP ROM for a little while but once CM is set, im moving.
I'm having a big problem with my Nexus 4 here lately. I tried to root it about 2 days ago, and it did not work. So i downloaded TWRP and my computer read it the same as the Nexus 4 root toolkit by WugFresh. I opened TWRP and it asked me to flash or boot (it was on flash), and i think i clicked "Recovery" and it made my Nexus not boot up, it was just at the logo screen. Then i tried to flash TWRP to the bootloader and System and it flashed TWRP, now it won't go into android. It just takes me into the TWRP interface. In the TRWP interface there are 8 options( Install, Wipe, Backup, Restore, Mount, Settings, Advanced, and Reboot). I pressed "Reboot" and i when press System, Recovery, or Bootloader it tells me that the is no OS installed, I've looked up how to install OS back via WugFresh's toolkit, but it's still not working (maybe because I'm on a old computer). So I'm kinda panicking, is there anyone i can call,or take my phone to, or can you guys help PLEASE!?!
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Okay, i'll try that right now..
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Yiddish said:
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Click to expand...
Click to collapse
Try install these drivers: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
chromium96 said:
Try install these drivers
Click to expand...
Click to collapse
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Yiddish said:
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Click to expand...
Click to collapse
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
chromium96 said:
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
Click to expand...
Click to collapse
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Yiddish said:
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Click to expand...
Click to collapse
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
Oh, i see. Okay here i go
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
Okay, it got past the Google screen, now it's been on the multicolored X for about 10 minutes+ not doing anything
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
How long will i be on the X loading screen??
Yiddish said:
How long will i be on the X loading screen??
Click to expand...
Click to collapse
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Thanks! I think it was just the ROM i chose. I just downloaded Slim Bean, this seems to be working( the startup screen looks cool ) I'm on the "Android is upgrading..." screen and it says "Starting apps." at the moment.
Okay, SlimBean took more than 10 minutes, so i factory reset and tried again, and it's still not booting up. ):
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Any ideas why it's still not working??
Yiddish said:
Any ideas why it's still not working??
Click to expand...
Click to collapse
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
BobWalker said:
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
Click to expand...
Click to collapse
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Yiddish said:
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Click to expand...
Click to collapse
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
BobWalker said:
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
Click to expand...
Click to collapse
Where do i get Gapps??
Modified boot.img of a rom is required to be flashed on that rom so that it works with TWRP.
Enabling ADB during first boot creates a way out in case your phone bootloops or stuck at MI logo and also hardbricked.
Many people hardbricked their phone while flashing MIUI based roms through TWRP, and they had to test-point to bring their phone back to life, my mod enables adb during boot and so people who used my mod and hardbricked their phone can access adb when their phone is stuck at MI logo or bootlooping and thus revive their phone.
Tools needed:-
1)Notepad++ (google it and download)
2)Android Image Kitchen(AIK) http://forum.xda-developers.com/attachment.php?attachmentid=3638835&d=1454959265
Steps:-
1)Download the required rom and extract its boot.img
2)Copy the boot.img to AIK folder and drag boot.img and drop it on unpackimg.bat
3)Open ramdisk folder and look for default.prop , open them with Notepad++
4)Editing default.prop Note:- This will enable adb at first boot
5)Change
Code:
ro.secure=1 to ro.secure=0
ro.adb.secure=1 to ro.adb.secure=0
ro.debuggable=0 to ro.debuggable=1
persist.sys.usb.config=none to persist.sys.usb.config=adb
delete the line ro.secureboot.devicelock=1 if present
OR (Alternate way)(recommended)
open ramdisk and look for fstab.qcom, open with notepad++ and search for ",verify" (without quotes) and delete it and save.
6)Now execute repackimg.bat, a image-new.img file will be compiled.
7)Flash the image-new.img through TWRP or through fastboot using "Fastboot flash boot image-new.img"
That's all
P.S:- Remember only use Boot.img specific for the miui version you wanna run, boot.img version not matching with MIUI version
will cause the Wifi to stop working.
Press thanks If this helped.:good:
Any queries feel free to ask me.:laugh:
Does the modified boot.img procedure need to be done for every ROM or just for the MIUI ROMs? I want to install the AOSP ROM and later CM 13 but I'm still not sure about the whole flashing process.
Sent from my Redmi Note 3 using XDA-Developers mobile app
SkinCoffin said:
Does the modified boot.img procedure need to be done for every ROM or just for the MIUI ROMs? I want to install the AOSP ROM and later CM 13 but I'm still not sure about the whole flashing process.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
modified boot.img is only for official MIUI roms, all other roms doesnt need it
Rajdip said:
modified boot.img is only for official MIUI roms, all other roms doesnt need it
Click to expand...
Click to collapse
So if I'm on Miui Official Global ROM 7.2.3 all I have to do is flash TWRP through fastboot, boot into it and flash the new ROM+GApps through it?
SkinCoffin said:
So if I'm on Miui Official Global ROM 7.2.3 all I have to do is flash TWRP through fastboot, boot into it and flash the new ROM+GApps through it?
Click to expand...
Click to collapse
exactly
Rajdip said:
exactly
Click to expand...
Click to collapse
Thank you! I just did it. It has booted and almost over in the "Optimizing apps" window. Thing is, I did forget to wipe system, data and cache before flashing, should I do it again or will it be fine like this?
EDIT: I rebooted the phone into recovery, wiped system, data and cache, flashed the ROM zip and wiped cache and dalvik cache. I booted the phone and it showed the Mi logo, then 4 circles screen flying around (green, red, blue and yellow) and it has been like this for like 5 min now.. Did I do something wrong? I'm starting to worry to be honest.
SkinCoffin said:
Thank you! I just did it. It has booted and almost over in the "Optimizing apps" window. Thing is, I did forget to wipe system, data and cache before flashing, should I do it again or will it be fine like this?
EDIT: I rebooted the phone into recovery, wiped system, data and cache, flashed the ROM zip and wiped cache and dalvik cache. I booted the phone and it showed the Mi logo, then 4 circles screen flying around (green, red, blue and yellow) and it has been like this for like 5 min now.. Did I do something wrong? I'm starting to worry to be honest.
Click to expand...
Click to collapse
it takes time to boot for the first time, did it boot now?
Rajdip said:
it takes time to boot for the first time, did it boot now?
Click to expand...
Click to collapse
Still hasn't booted. It has been on the flying circles screen for around 10 minutes now. Maybe fastboot twrp again and do the process all over again?
SkinCoffin said:
Still hasn't booted. It has been on the flying circles screen for around 10 minutes now. Maybe fastboot twrp again and do the process all over again?
Click to expand...
Click to collapse
Try again, goto TWRP, wipe system,data,cache,dalvik and flash the rom. Now reboot...
Rajdip said:
Try again, goto TWRP, wipe system,data,cache,dalvik and flash the rom. Now reboot...
Click to expand...
Click to collapse
So I shouldn't reinstall TWRP through fastboot?
EDIT: Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.
SkinCoffin said:
So I shouldn't reinstall TWRP through fastboot?
Click to expand...
Click to collapse
No, first try what I said, dont wipe cache and dalvik after the rom is flashed
Rajdip said:
No, first try what I said, dont wipe cache and dalvik after the rom is flashed
Click to expand...
Click to collapse
Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.
SkinCoffin said:
Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.
Click to expand...
Click to collapse
okay
i do exactly like your tutor...i edit boot.img n delete ",verify"
repack than delete original boot.img, than use moded boot.img... but wifi doesn't work...
where my mistake...?
Mayoz said:
i do exactly like your tutor...i edit boot.img n delete ",verify"
repack than delete original boot.img, than use moded boot.img... but wifi doesn't work...
where my mistake...?
Click to expand...
Click to collapse
are you sure you are using the boot.img of the MIUI version you are flashing? there is two 7.2.3.0 version of boot.img one for global and one for china. Anyway try this and see if wifi works, goto TWRP(I hope you've already deleted the emmc_appsboot file), select mount and then tick on mount system as read only. Then flash the rom. This method will replace TWRP with MIUI recovery but your wifi should start working.
Rajdip said:
are you sure you are using the boot.img of the MIUI version you are flashing? there is two 7.2.3.0 version of boot.img one for global and one for china. Anyway try this and see if wifi works, goto TWRP(I hope you've already deleted the emmc_appsboot file), select mount and then tick on mount system as read only. Then flash the rom. This method will replace TWRP with MIUI recovery but your wifi should start working.
Click to expand...
Click to collapse
yes using the boot.img of the MIUI version to flashing...from recovery rom stable 7.2.3.0 china....maybe my mistake i replace emmc_appsboot file from miui forum...not delete "will replace TWRP with MIUI recovery...' still can booting? i already UBL...
Mayoz said:
yes using the boot.img of the MIUI version to flashing...from recovery rom stable 7.2.3.0 china....maybe my mistake i replace emmc_appsboot file from miui forum...not delete "will replace TWRP with MIUI recovery...' still can booting? i already UBL...
Click to expand...
Click to collapse
I didnt get you, can you be more clear?
Do I need to use Windows 64bits to flash TWRP?
Thanks.
pepemonje said:
Do I need to use Windows 64bits to flash TWRP?
Thanks.
Click to expand...
Click to collapse
no need 32bit works
Hello, I've followed a certain tutorial and flashed a fastboot Rom with modified emmc file in attempt to unlock bootloader by force because, even after two weeks of trying, I can't get a confirmation SMS from xiaomi to confirm sending an unlock request. After doing it and flashing TWRP onto my device, I'm still unable to enter recovery. Just shows a picture of device and a disconnected usb cable. I need to flash SuperSU in order to get root access.
Because this device is getting me really confused, please answer a couple of questions for me.
If I flash a recently uploaded global stable ROM 7.2.3.0. and flash TWRP with a modified boot image from this tutorial, will I finally be able to enter recovery and install SuperSU?
Flashing will probably relock my bootloader. Is it possible for me to finally enter TWRP and flash SuperSU after flashing the new boot image?
I've thought that I could enter TWRP just by unlocking the bootloader but it seems that I've missed something. I can't remember last time a phone got me this confused.
My only goal here is being able to enter TWRP and rooting my phone, I gave up on unlocking the bootloader officially because I can't ever get that confirmation SMS.
I appreciate the help!! :fingers-crossed: