Database Info

[Q] home to root

please dont shout, just take pitty on me.
I have been getting into the world of rooting and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not fully understanding exactly what im doing.
but i can flash by:
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
PS
my cid is VADAP001
my MID is PG5813000

taffytim said:
please dont shout, just take pitty on me.
I have been getting intot he world of routing and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not flly understanding exactly what im doing.
but i can flashing by
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
Click to expand...
Click to collapse
Hi,
Are you talking about wifi?
Have you got a router?

When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.

Malybru, i do have a router but my wifi wont turn on so i cant connect to it.

T-Macgnolia said:
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?

taffytim said:
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
Click to expand...
Click to collapse
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.

T-Macgnolia said:
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
Click to expand...
Click to collapse
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?

For every custom rom you install you need to follow the same procedure.
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot (some rom's have more than one kernel then choose the best you want)
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
sent from my blazing fast pyramid through sonic waves

ta gane shp, this is a good place with good people

Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?

Asskicker2 said:
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Click to expand...
Click to collapse
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.

malybru said:
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
Click to expand...
Click to collapse
Yeah, that isn't working.
Wifi ain't working now.

Asskicker2 said:
Yeah, that isn't working.
Wifi ain't working now.
Click to expand...
Click to collapse
Hi,
Just restore the nandroid backup you made.

malybru said:
Hi,
Just restore the nandroid backup you made.
Click to expand...
Click to collapse
Yeah, but I wanted to update to newest kernel. Thanks though

Doesn't work with me.
taffytim said:
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
Click to expand...
Click to collapse
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!

Wi-Fi Issues
theumairahmad said:
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Click to expand...
Click to collapse
Post 3 in this thread explains exactly where the problem is. But ........you will never unlock that boot partition if ur phone is S-ON. The trick with the wire works...it took me couple of times to do it but it worked. Then.....the lates ViperS version does it for you. You do not have to use ADB or whatever that program was to flash the boot.img It is all in the ROM. I even flashed the newest bricked 1.4 kernel on top.....but that 3rd comment is the key to all problems with Wi-Fi and other kernel issues:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:

[Q] A700 Bricked Help!!!!!

Hi everyone,
this is the first time i post in this forum and i am totally beginner to the andriod system.....And i do think i am exactly in the same status with nicolas(http://forum.xda-developers.com/showthread.php?p=33211630)----my a700 bricked beacuse proceed ICS root's procedures in jb system
i have tried MD instruction to get into fastboot mode....but i dont know if i get into fastboot mode:
i only get "acer" logo in the middle and i have two statement at the top left corner:
"Bootloader version JB-653b3d3 (Unlock Mode)
Bootloader VJB-653b3d(UnlockMode): Starting Fastboot USB download protocol"
When i open "window device manager" in PC, it showed "ADB interface"-"Acer fastboot interface"
Have i got into fastboot mode?
what is my next step then?????:crying::crying::crying::crying:
i dont know how can i copy image from Verboth's ROM(http://forum.xda-developers.com/showthread.php?t=1952124)
THX A LOT!!!!!!!!!!!!!!

hksrichard said:
Hi everyone,
this is the first time i post in this forum and i am totally beginner to the andriod system.....And i do think i am exactly in the same status with nicolas(http://forum.xda-developers.com/showthread.php?p=33211630)----my a700 bricked beacuse proceed ICS root's procedures in jb system
i have tried MD instruction to get into fastboot mode....but i dont know if i get into fastboot mode:
i only get "acer" logo in the middle and i have two statement at the top left corner:
"Bootloader version JB-653b3d3 (Unlock Mode)
Bootloader VJB-653b3d(UnlockMode): Starting Fastboot USB download protocol"
When i open "window device manager" in PC, it showed "ADB interface"-"Acer fastboot interface"
Have i got into fastboot mode?
what is my next step then?????:crying::crying::crying::crying:
i dont know how can i copy image from Verboth's ROM(http://forum.xda-developers.com/showthread.php?t=1952124)
THX A LOT!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Eh.... another one
Mate, you probably only need to fastboot a JB 700 boot.img on your tab.
Yes, you are in fastboot mode.
So if I get this right, you have a JB operating system, but you decided to use an ICS root procedure?
If you haven't changed anything else, it should be simple enough as running Verboth's 700 JB easy root program. If you don't want to do the whole thing, then you can simply install his boot.img by using fastboot.
fastboot flash boot xxxxxxxxx.img (where xxxxxxxx.img is the name of the boot.img)
Did you attempt to install some type of update file? Just asking to be sure I know exactly how you got to this situation.
MD

Moscow Desire said:
Eh.... another one
Mate, you probably only need to fastboot a JB 700 boot.img on your tab.
Yes, you are in fastboot mode.
So if I get this right, you have a JB operating system, but you decided to use an ICS root procedure?
If you haven't changed anything else, it should be simple enough as running Verboth's 700 JB easy root program. If you don't want to do the whole thing, then you can simply install his boot.img by using fastboot.
fastboot flash boot xxxxxxxxx.img (where xxxxxxxx.img is the name of the boot.img)
Did you attempt to install some type of update file? Just asking to be sure I know exactly how you got to this situation.
MD
Click to expand...
Click to collapse
Thx for yr help so i have the command of flashing img!!! i havent attempt any update file or other things but i have clicked the factory reset once...does it matter???
Do u prefer the img inside the easy root or iconiaN2.6??? i dont know which one i should choose??? my version is jelly bean 4.1.1
so after i download it, do i have to move the boot.img to the sdk/platform-tools folder???
or do i just download it any place, then change the directory in the Window Command Prompt to the Rom folder???
lets say "cd C:\ iconiaN 2.6"?? then "C:\ iconiaN2.6\fastboot flash boot boot.img"??
Thz for yr patience...

Moscow Desire said:
Eh.... another one
Mate, you probably only need to fastboot a JB 700 boot.img on your tab.
Yes, you are in fastboot mode.
So if I get this right, you have a JB operating system, but you decided to use an ICS root procedure?
If you haven't changed anything else, it should be simple enough as running Verboth's 700 JB easy root program. If you don't want to do the whole thing, then you can simply install his boot.img by using fastboot.
fastboot flash boot xxxxxxxxx.img (where xxxxxxxx.img is the name of the boot.img)
Did you attempt to install some type of update file? Just asking to be sure I know exactly how you got to this situation.
MD
Click to expand...
Click to collapse
ar...i have forgotten to answer yr last q...How i get to this situation??
After googling, all webs say 4.2 is jelly bean and 4.0 is ICS...i guess i am ICS i am so careless
then i follow yr thread instruction..i try method1. it still okay i can run the system but i cant root it. So i try the second method...
doing factory reset is after i have bricked..does it matter??

Moscow Desire said:
Eh.... another one
Mate, you probably only need to fastboot a JB 700 boot.img on your tab.
Yes, you are in fastboot mode.
So if I get this right, you have a JB operating system, but you decided to use an ICS root procedure?
If you haven't changed anything else, it should be simple enough as running Verboth's 700 JB easy root program. If you don't want to do the whole thing, then you can simply install his boot.img by using fastboot.
fastboot flash boot xxxxxxxxx.img (where xxxxxxxx.img is the name of the boot.img)
Did you attempt to install some type of update file? Just asking to be sure I know exactly how you got to this situation.
MD
Click to expand...
Click to collapse
At last, I have chosen the boot.img in the easy root zip from Verboth...but i type the flash command it said it does not recognized.
BUT after i move the boot.img into the platform-tools next to the fastboot.exe, i type the command again and it works!!!!!!!!!!!!!!!!!!!!!!!!!
Thx a lot!!!!!!!!!!!!!!!!!!!!!!!!!1
my tablet is back!!!!!!!!!!! i can go back to the normal mode !!!!!
One last question about the root...so after i done all these step, can my A700 still follow yr easy root guide in here???: http://forum.xda-developers.com/showthread.php?t=1997350
my A700 details:
Andriod Version: 4.1.1
Kernel version: 3.1.10+
Image version: Acer_AV051_A700_RV18RC02_PA_CA
Build number: Acer_AV051_A700_1.053.00_PA_CA
Image P/N: FM.S1MA0.04F
can i still root by easy root??? looking forward to hearing yr gd news
anyway, you are very kind moderator, thx!

My computer doesn't recognize the A700 tablet. It say <waiting for device> after I try the boot.img command.

See daily results of ceribenanoche. Sinuano Noche

alan0923 said:
My computer doesn't recognize the A700 tablet. It say <waiting for device> after I try the boot.img command.
Click to expand...
Click to collapse
I figure it's issue with Windows 10. All the adb drivers are for windows 7. Ran on a computer running windows 7 and there is response showing bootloader locked. Will look at the other posts and continue. Thanks for all the posts on XDA.
I got the other computer on windows 10 to recongize the tablet as well now.

Half bricked Xoom, deleted everything - help appreciated

Hello,
again i need help I have unlocked the bootloader on my Xoom, the i have flashed TWRP and downloaded a Rom and the Gapps. I copied the gapps onto the device and followed instructions which came with the rom. I was instructed to wipe "system" too which i did.
Of course that deleted the downloaded rom and gapps too. Now i have TWRP and was excited to mount USB storage and just copy over again the rom and gapps but unfortunately there is no mount as USB option.
What and how is the smartest way to go about it? I wanted to sideload over ADB but the device is not found. I have really tried everythin in my knowledge, hope someone can help
cheers

Come on guys, really need help here. My kids are killing me for the damn thing

I have same problem.......it's an issue of twrp !

Have you tried a micro sd card? (copy the rom and gapps there from a pc then put it in the Xoom, etc...)
Worst case, you should be able to grab the stock images http://forum.xda-developers.com/wiki/Motorola_Xoom and fastboot flash the device back to stock.

Have the same problem
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?

hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
Stock flash doesnt require adb, just fastboot mode. You may need to still install a driver, but if you can boot into recovery then the xoom should also be able to boot into fastboot mode and be recognized by a pc. If the instructions on the link I gave arent enough, I will see if I cant find something tomorrow when I am on a pc.
Sent from my GT-N8013 using XDA Premium 4 mobile app

hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .

Solved
airesch said:
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .
Click to expand...
Click to collapse
Hey airesch, thank you for your support. I couldn´t follow yours suggestion because my xoom was not recognizing the PC or MAC. However I discovered that my sdcard was broken. When I´ve tried a new one with ZIP files inside it works perfectcly and I could return to my old room doing flah in the recovery mode of TWRP2.2.
It is important to note that my Xoom did not find .IMG files inside the card but only ZIP ones. Any way it worked perfectly and I hope this solution will serve to other in solving his/her problems.
Many thanks

Well, that works too, and that was closer to what I originally suggested (tho I didn't expect you had a bad sd card.)
And yes, recoveries generally don't support IMG files directly, you need to have a specially crafted zip to flash those in. IMG files directly are for fastboot/pc tool flashing.
Congrats on fixing it.

system update disrupted..

guys, my sister's nexus 5 got an update but while downloading wifi got disconnected and from that point onwards wifi and bluetooth arent working... its still in 4.4.4, any solutions??

Download the lollipop factory image from google, and install it using fastboot.

roh756 said:
guys, my sister's nexus 5 got an update but while downloading wifi got disconnected and from that point onwards wifi and bluetooth arent working... its still in 4.4.4, any solutions??
Click to expand...
Click to collapse
When you flash the image make sure you remove the -w in fastboot update in batch file.

thank you, but i dont have android sdk installed in my computer, is it really necessary for sdk to be installed inorder to go to fastboot from cmd?
or i'll do one thing, i'll install a custom recovery and install factory rom from there.. is it ok to do that?

Lokke9191 said:
Download the lollipop factory image from google, and install it using fastboot.
Click to expand...
Click to collapse
thank you, but i dont have android sdk installed in my computer, is it really necessary for sdk to be installed inorder to go to fastboot from cmd?
or i'll do one thing, i'll install a custom recovery and install factory rom from there.. is it ok to do that?

roh756 said:
thank you, but i dont have android sdk installed in my computer, is it really necessary for sdk to be installed inorder to go to fastboot from cmd?
or i'll do one thing, i'll install a custom recovery and install factory rom from there.. is it ok to do that?
Click to expand...
Click to collapse
You run the risk of having bugs like you do now if you use a flashable zip through a custom recovery. Ya, download the sdk. I wouldnt use the flash all bat either. Id fastboot flash each image individually, while rebooting the bootloader in between each image just to be safe. Fastboot reboot-bootloader. Once you have the sdk setup, and read a quick tutorial on fastboot, youll realize how fast and simple it is to use fastboot. You can find really good guides on how to setup and use fastboot.

Lokke9191 said:
You run the risk of having bugs like you do now if you use a flashable zip through a custom recovery. Ya, download the sdk. I wouldnt use the flash all bat either. Id fastboot flash each image individually, while rebooting the bootloader in between each image just to be safe. Fastboot reboot-bootloader. Once you have the sdk setup, and read a quick tutorial on fastboot, youll realize how fast and simple it is to use fastboot. You can find really good guides on how to setup and use fastboot.
Click to expand...
Click to collapse
ok man, thanks a lot..

Trying to flash TWRP Recovery image & Root G8142 on Ubuntu - Need Help

Hi All,
I had a previously rooted 8142, but it crapped out on me last week, so I've just bought a new one. I'm trying to root it now. I've unlocked bootloader, and installed the TWRP app, but I can't figure out how to root it.
I was running windows and used Xperifix when I did my last one, but now I'm using Ubuntu, and there's not really any software (like Xperifix or One Click Root) available.
I've been using FlashTool, and can get it to show root privelages, but I have no idea how to flash a recovery image using it.
I tried using Platform Tools via the terminal and I think I was able to flash a TWRP recovery image to the device, but the TWRP app isn't seeing it, nor can I boot into recovery mode.
I tried to download a recovery image via the TWRP app, but even when it's downloaded, the TWRP app isn't finding any recovery images despite pointing the app to my downloads folder.
TWRP is also showing "No Root Permissions"
I can't flash SuperSu or any other ROM's without being able to boot into TWRP recovery menu.
Maybe I'll have to install windows to use the rooting software. Does anyone have any ideas? Been messing around with it 6 hours now and still can't boot into recovery.
Thanks for any ideas.

first I dont know if youre using fastboot so do "sudo apt install android-tools-adb android-tools-fastboot" then open a terminal were twrp is located and type fastboot flash recovery "name of twrp".img and then you are ready to go. I dont know if you can use this phone without a specific driver so that can be a problem. If you cant do it that way i recommend you using a virtual machine with windows and run fastboot (platform tools trough there) so you dont have to remove ubuntu.
Also remember how to access fastboot

ricardo99831390 said:
first I dont know if youre using fastboot so do "sudo apt install android-tools-adb android-tools-fastboot" then open a terminal were twrp is located and type fastboot flash recovery "name of twrp".img and then you are ready to go. I dont know if you can use this phone without a specific driver so that can be a problem. If you cant do it that way i recommend you using a virtual machine with windows and run fastboot (platform tools trough there) so you dont have to remove ubuntu.
Also remember how to access fastboot
Click to expand...
Click to collapse
Thanks! I'll try both of those methods over the weekend and report back.

tombow said:
Thanks! I'll try both of those methods over the weekend and report back.
Click to expand...
Click to collapse
well i forgot to mention, the fastboot flash recovery command depends on your android version so take that in count.