This is a stock kernel, except that adb root is permanent.
Removes the need for psneuter if you lose root access for whatever reason.
Flash via fastboot, cwr appears to still not work on kernels.
Code:
fastboot flash boot boot.img
http://www.mediafire.com/?qyk3mv5gns11epg
Pure Awesomeness...LOL...Nice BUD!
still can't get adb to recognise my phone in fastboot... I tried every driver that I have found an windows says that no driver is available... windows 7/64bit
Install HTC sync 3.
Also, adb and fastboot are mutually exclusive.
I use OSX, I grabbed the fastboot for mac binaries from HTC's website. But I can't get fastboot to run and flash the image. HTC says I should place fastboot anywhere on my system and then navigate to its path to use it but that just isn't working?
vdefender said:
I use OSX, I grabbed the fastboot for mac binaries from HTC's website. But I can't get fastboot to run and flash the image. HTC says I should place fastboot anywhere on my system and then navigate to its path to use it but that just isn't working?
Click to expand...
Click to collapse
Put it in the tools folder of the sdk...
two_cents said:
still can't get adb to recognise my phone in fastboot... I tried every driver that I have found an windows says that no driver is available... windows 7/64bit
Click to expand...
Click to collapse
This driver worked for me win_x/64bit
http://forum.xda-developers.com/showthread.php?t=878786
Sent from my ADR6400L using XDA App
I'm currently trying to install your other kernal, and after I moved my Fastboot.exe file into the platform-tools folder and executed Fastboot boot boot.img my command prompt is stuck at < waiting for device >
I cannot input anything into the command prompt, but I have control over my phone in fastboot.
any advice????
nvm
installed htc sync 3... coming from unrevoked I didn't install this cause they said it interferes with the root pkg... all this adb stuff i'm starting to actually like adb commands... just got to watch the typos... fasboot doesn't do anything lol
Make sure you set fastboot-mac or fast boot as chmod 755
chmod 755 ./fastboot
Click to expand...
Click to collapse
Then you would run it like
./fastboot flash boot boot.img
Click to expand...
Click to collapse
Always add the ./ before each adb command and fastboot command when using a mac. I had to learn that the hard way back in the day.
THATTON said:
Always add the ./ before each adb command and fastboot command when using a mac. I had to learn that the hard way back in the day.
Click to expand...
Click to collapse
I had to do this in ubuntu as well
Sent from my ADR6400L using XDA App
adrynalyne said:
This is a stock kernel, except that adb root is permanent.
Removes the need for psneuter if you lose root access for whatever reason.
Flash via fastboot, cwr appears to still not work on kernels.
Code:
fast boot flash boot boot.img
http://www.mediafire.com/?qyk3mv5gns11epg
Click to expand...
Click to collapse
Shouldnt fasboot in the code up there be connected? fastboot not fast boot. noobs'll freak. lol Thanks Adryn, this makes it a lot nicer.
How does this compare to the kernal in your rom thread? Coming from a DX, I'm new to the kernal stuff. Thanks.
two_cents said:
still can't get adb to recognise my phone in fastboot... I tried every driver that I have found an windows says that no driver is available... windows 7/64bit
Click to expand...
Click to collapse
Best thing for me , win 7 32, downloaded and installed pdanet from market, downloaded drivers to SD, mount as disk , install pda stuff off SD, and bam adb worked great , don't know if this ? Has been answered yet , haven't got that far in the thread
Sent from the Swag HTC Thunderbolt - ADR6400L using XDA Premium App
ran the flash, fastboot tells me that both went ok. but all my info still tells me 1.12.605.6 for build and software number. is there anything i can see that i know it changed. kernal states
2.6.32.21-gb05544a
[email protected] 18-2 #1
tue mar 1 16:38:55 CST 2011
Instructions: How to flash boot.img via fastboot For Mac
Requirements:
Rooted Thunderbolt
Ability to boot into the bootloader. (I used "./adb reboot bootloader")
1. Download fastboot-mac.zip and the boot.img
2. unzip and place fastboot-mac into your platform-tools folder
3. Place the downloaded boot.img into your platform tools folder
4. Open terminal and cd your platform-tools folder
5. Run "chmod 755 ./fastboot-mac"
6. Now run "./fastboot-mac devices"
7. You should see "HTxxxxxxxxxx fastboot" after running previous commands
8. Now to flash just run "./fastboot-mac flash boot boot.img"
9. it should say "sending 'boot' (3008 KB)... OKAY" and "writing 'boot'... OKAY"
Your Good to Go
10. Thank adrynalyne for the kernel
Also thank you tavella for the chmod 755 part of this.
Finally team AndIRC, Jcase and all.
Enjoy!!! PM me if i have made a mistake or if you have something to add.
icedmayhem said:
ran the flash, fastboot tells me that both went ok. but all my info still tells me 1.12.605.6 for build and software number. is there anything i can see that i know it changed. kernal states
2.6.32.21-gb05544a
[email protected] 18-2 #1
tue mar 1 16:38:55 CST 2011
Click to expand...
Click to collapse
March 1st kernel is the correct updated kernel... February is the stock kernel... You are runningthe stock .6 rom... Adryn has the .9 as a bloat free rom
Sent from my ADR6400L using XDA App
Ty
Sent from my ADR6400L using XDA App
You've done it again adryn, thanks and much appreciated as always.
Sent from my ADR6400L using XDA App
Related
I'm in a bit of jam. I flashed the official zip from google to update to 4.2.2 and the flash seemed to work fine. I cleared both caches after the update
However, now I seem to be completely locked out of adb and the phone doesn't prompt me for authorization (the new feature in 4.2.2) http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ . I am showing connected but offline just like this article. I have tried multiple reboots (phone/computer) as well as different USB ports. I have not tried another computer yet.
When I try to go to recovery I get a red exclamation point dead robot as I assume the flash wiped TWRP and I can't reflash TWRP without adb/root.
I would like to try to avoid a complete internal memory factory reset from the rom which I'm not sure would work anyway.
Please help.
update your adb / sdk.
bodh said:
update your adb / sdk.
Click to expand...
Click to collapse
Fortunately, I was able to reflash TWRP using fastboot w/o using adb. At the bootloader, I ran
Code:
fastboot flash recovery recovery.img
which got my recovery back up and running.
I decided to do a factory wipe and even after that adb was showing as offline and not prompting. I am very confident that your suggestion of updating the platform tools is going to fix my issue.
Thank you.
Locked on 4.2.2
My Nexus 7 is locked on 4.2.2. I tried to Unlock with Nexus Root Toolkit and I get "adb offline". I did the command "adb devices" and the device showed up, but when I tried to unlock again, it gets stuck on "checking adb status". I updated SDK and copied the new adb.exe, fastboot.exe, etc into the platform-tools folder and it still doesnt work. So basically my oem is locked on 4.2.2 and I can get adb or the toolkit to work properly.. Is there a way to downgrade back to 4.2.1 or get the Wugfresh Nexus Toolkit to actually unlock my Nexus 7 on 4.2.2??
Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.
bodh said:
Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.
Click to expand...
Click to collapse
If you know the steps or can link me to a page, that would be much appreciated. I want clear steps.
Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.
Why cant people wait..
lol
Bronk93 said:
Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.
Click to expand...
Click to collapse
I'm going to try this. Can i just type "fastboot devices" in the command prompt and it'll work?
EDIT: I found a simple fix for anyone with this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.
AJ Bryant said:
I'm going to try this. So would I have to copy a fastboot.exe into the platform-tools folder? Or can i just type "fastboot devices" in the command prompt and it'll work?
Click to expand...
Click to collapse
If you downloaded the new android sdk fastboot should already be in there
I found a simple fix for this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.
---------- Post added at 12:05 PM ---------- Previous post was at 11:55 AM ----------
XX-RAZOR-XX said:
Why cant people wait..
lol
Click to expand...
Click to collapse
No need to wait because I found the fix, by myself.
Can't wait to get home and try this. I got stuck last night at adb offline
Sent from my Nexus 4 using xda app-developers app
But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895
bodh said:
But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
That's the point; we want to be unlocked and rooted on 4.2.2. I previously thought that in order to get an unlocked and rooted Nexus, I'd have to be on 4.2.1, unlock and root, then upgrade to 4.2.2 but that's not the case. I just unlocked and rooted via ADB since the Nexus Root Toolkit wasn't working for 4.2.2. I (and probably others) kept getting the "adb offline" error even after allowing USB debugging between the device and PC. Point is, if you're on 4.2.2 with a locked bootloader, you'll need to unlock and root using ADB commands. I don't know how many people have this issue but if someone requests it, I'll just post the steps on how to unlock and root 4.2.2 jelly bean using the ADB commands.
Re: [Q]Manually updated to 4.2.2... Now locked out of adb and recovery. Help
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app
Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.
bodh said:
Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.
Click to expand...
Click to collapse
What do u mean by terminal on my PC fast boot cwm.img
Sent from my Nexus 4 using xda app-developers app
Rooting Jelly Bean 4.2.2 via ADB
DowntownJeffBrown said:
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.
AJ Bryant said:
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.
Click to expand...
Click to collapse
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app
DowntownJeffBrown said:
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
For the Nexus 4 use this cwm image instead: http://download2.clockworkmod.com/re...0.2.3-mako.img
When youre doing the fastboot recovery, put in the name of this img file at the end. "fastboot flash recovery [name of the download file].img
Hey guys,
I've been looking for a tutorial that explains how I can manually install Googles official occam-krt16s firmeware on my Nexus 4 currently running 4.3 JWR66V (maybe important side note: I haven't JWR66Y installed, some tutorials ask for this). All tutorials I've seen install the firmware from scratch and – as I understand it – delete everything with it (so I figure my Titanium backups will be gone in that case, as user data and personal files will be deleted?). Or use CWM and flash radio, BL and ROM manually like in AppReviewBros YT video about ‘How to Install Stock Android 4.4 KitKat on Nexus 4‘, sorry can't post links here. But is this official stuff?
What would you recommend?
Can I not just install occam-krt16s via CWM and do a wipe/clear cache beforehand? Does googles firmware not include the radio & bootloader files? Sorry I'm a bit stupid here I guess.
My device is unlocked, rooted and running CWM 6.0.4.3., SuperSU 1.80 and JWR66V.
Thanks for any input/links etc.
Connect the device, download and unzip the .tgz factory image, and run flash all.bat
Sent from my Nexus 4 using Tapatalk
RealSlimShadyMC said:
Connect the device, download and unzip the .tgz factory image, and run flash all.bat
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Hey, there –
I understand transferring the files to my device first and then flash via CWM doing a wipe first? And this will preserve my backups?
Team_Cheesecake said:
Hey, there –
I understand transferring the files to my device first and then flash via CWM doing a wipe first? And this will preserve my backups?
Click to expand...
Click to collapse
Run the script via your computer, with the device connected. I suggest you use wugfresh's toolkit to back up all your stuff, and if I were you I would copy the backups from the backup directory to your computer. Using flashall.bat wipes everything, so be careful.
Sent from my Nexus 4 using Tapatalk
RealSlimShadyMC said:
Run the script via your computer, with the device connected. I suggest you use wugfresh's toolkit to back up all your stuff, and if I were you I would copy the backups from the backup directory to your computer. Using flashall.bat wipes everything, so be careful.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thank you, RealSlimShadyMC…
Can't use wugfresh's toolkit unfortunately, as I'm not on a windows pc. Is there another way of backing up my user data, Titanium backup style and transfer the files to my computer?
Mac or Linux? There are other toolkits available for those platforms
Sent from my Nexus 4 using Tapatalk
givainH joined
RealSlimShadyMC said:
Mac or Linux? There are other toolkits available for those platforms
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Mac. All toolkits I've seen for Mac just allow to root, install CWM etc…?
I'm not really sure. Just try to do a titanium backup to your SD card and then copy the folder to your mac
Sent from my Nexus 4 using Tapatalk
Just edit the flash-all.bat file and remove -w and then run it.
Now your data will nto be wiped.
Ibrahim.Rahman said:
Just edit the flash-all.bat file and remove -w and then run it.
Now your data will nto be wiped.
Click to expand...
Click to collapse
Hey there,
thanks – can I do that coming from ancient 4.3 JWR66V or would you recommend updating at least to KRT160 before?
Team_Cheesecake said:
Hey there,
thanks – can I do that coming from ancient 4.3 JWR66V or would you recommend updating at least to KRT160 before?
Click to expand...
Click to collapse
You can do that from ANY android version. This will update you to KRT16S, and afterwards you can ADB sideload the 4.4.1 .zip
Sent from my Nexus 4 using Tapatalk
RealSlimShadyMC said:
You can do that from ANY android version. This will update you to KRT16S, and afterwards you can ADB sideload the 4.4.1 .zip
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Awesome! Thanks so much!!
Team_Cheesecake said:
Hey there,
thanks – can I do that coming from ancient 4.3 JWR66V or would you recommend updating at least to KRT160 before?
Click to expand...
Click to collapse
Yes, I believe, since you are flashing a complete factory image, you can flash your phone running 4.3 JWR66V.
Weird… When I try ./flash-all.sh (edited the -w out before) Terminal tells me:
./flash-all.sh: line 17: fastboot: command not found
./flash-all.sh: line 18: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 21: fastboot: command not found
./flash-all.sh: line 23: fastboot: command not found
…and nothing happens. My Nexus is in bootloader mode and flash-all.sh is in the same folder as fastboot and adb
Also when I check for ./fastboot devices it states my devices serial number however it also says:
ERROR: could not get pipe properties
…that's new :-/
Team_Cheesecake said:
Weird… When I try ./flash-all.sh (edited the -w out before) Terminal tells me:
./flash-all.sh: line 17: fastboot: command not found
./flash-all.sh: line 18: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 21: fastboot: command not found
./flash-all.sh: line 23: fastboot: command not found
…and nothing happens. My Nexus is in bootloader mode and flash-all.sh is in the same folder as fastboot and adb
Also when I check for ./fastboot devices it states my devices serial number however it also says:
ERROR: could not get pipe properties
…that's new :-/
Click to expand...
Click to collapse
Type "./fastboot-mac" as the command and instead of just "./fastboot"
I believe pipe properties don't really affect anything.
Team_Cheesecake said:
Weird… When I try ./flash-all.sh (edited the -w out before) Terminal tells me:
./flash-all.sh: line 17: fastboot: command not found
./flash-all.sh: line 18: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 21: fastboot: command not found
./flash-all.sh: line 23: fastboot: command not found
…and nothing happens. My Nexus is in bootloader mode and flash-all.sh is in the same folder as fastboot and adb
Also when I check for ./fastboot devices it states my devices serial number however it also says:
ERROR: could not get pipe properties
…that's new :-/
Click to expand...
Click to collapse
Alright, just figured the problem out. The commands in flash-all.sh state as follows:
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
sleep 5
fastboot update image-occam-krt16s.zip
The reason Terminal stated that it couldn't find the fastboot command is because none of them started with ./fastboot . After editing the commands and saving flash-all.sh installation started, KitKat booted up and Android is currently optimising app 215 of 246 Yeay!!
Next step: Install 4.4.1 and make my girlfriend jealous
Congrats man if you want the 4.4.1 zip, just look in the forums.
BTW in case you need to know how to flash it, do fastboot reboot recovery. You should see a dead android. Press power and volume up together, and select sideload from the list. Then adb sideload the zip
Edit: btw, if you want some free extra performance, go to developer options and change the runtime to ART
Sent from my Nexus 4 using Tapatalk
RealSlimShadyMC said:
Congrats man if you want the 4.4.1 zip, just look in the forums.
BTW in case you need to know how to flash it, do fastboot reboot recovery. You should see a dead android. Press power and volume up together, and select sideload from the list. Then adb sideload the zip
Edit: btw, if you want some free extra performance, go to developer options and change the runtime to ART
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for all the help, gonna check that out later today. I'm just happy I finally figured it out with the help of you guys :good:
RealSlimShadyMC said:
Congrats man if you want the 4.4.1 zip, just look in the forums.
BTW in case you need to know how to flash it, do fastboot reboot recovery. You should see a dead android. Press power and volume up together, and select sideload from the list. Then adb sideload the zip
Edit: btw, if you want some free extra performance, go to developer options and change the runtime to ART
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Can also I flash the official OTA using this method? The list doesn't give me a sideload option though, I can select between:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
…I guess it could be option #2 ?
Team_Cheesecake said:
Can also I flash the official OTA using this method? The list doesn't give me a sideload option though, I can select between:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
…I guess it could be option #2 ?
Click to expand...
Click to collapse
Apply update from ADB
Sent from my Nexus 4 using xda app-developers app
I had stock android installed. And I had rooted. I tried to use flashify to install TWRP, but every time it rebooted it would go into fastboot mode. well, I didn't think it would be an issue if I decided to just let the stock update run it's course instead of flashing a rom. So I had the OTA for kitkat run. The phone rebooted, and will only boot into fastboot, and download mode. I need help to get back to stock of any form, root or no root. Please? I am quite far from any repair center at a hotel for the next few days, so Wi-Fi is quite slow.
i
eddytheyeti2 said:
I had stock android installed. And I had rooted. I tried to use flashify to install TWRP, but every time it rebooted it would go into fastboot mode. well, I didn't think it would be an issue if I decided to just let the stock update run it's course instead of flashing a rom. So I had the OTA for kitkat run. The phone rebooted, and will only boot into fastboot, and download mode. I need help to get back to stock of any form, root or no root. Please? I am quite far from any repair center at a hotel for the next few days, so Wi-Fi is quite slow.
Click to expand...
Click to collapse
at least u need to download another stock firmware to flash it through recovery
:good:
x102x96x said:
at least u need to download another stock firmware to flash it through recovery
:good:
Click to expand...
Click to collapse
I don't have a recovery. I'm at fastboot or download. No recovery...
i
eddytheyeti2 said:
I don't have a recovery. I'm at fastboot or download. No recovery...
Click to expand...
Click to collapse
so flash recovery by adb and then use recovery to install rom
:good:
Hit Thanks
flash twrp to it, while in fast boot using ADB
http://download1983.mediafire.com/k2ahkbsh07sg/wk6p32jj5hg2px9/twrp_2.6.3.3_loki-ls980.img
Cronic2009 said:
flash twrp to it, while in fast boot using ADB
http://download1983.mediafire.com/k2ahkbsh07sg/wk6p32jj5hg2px9/twrp_2.6.3.3_loki-ls980.img
Click to expand...
Click to collapse
Instructions please?
When I flash twrp, should I flash a nonstock rom, or stock? Can you direct me to stock downloads.
open command prompt in ADB and execute
fastboot flash twrpls980.img
*make sure you put the downloaded image in the adb folder or you will have to include the path to where the file is located.
I was on a stock ROM when I flashed it, here you can find some stock files. http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Cronic2009 said:
open command prompt in ADB and execute
fastboot flash twrpls980.img
*make sure you put the downloaded image in the adb folder or you will have to include the path to where the file is located.
I was on a stock ROM when I flashed it, here you can find some stock files. http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Click to expand...
Click to collapse
Can I get a link to download ADB for Windows 8? Is that all I need to type? What if I'm using a different recovery image?
What is the sprint stick rom from that download link?
sorry misread your previous post, those .zips are flashable through TWRP, here is a LS980 ZVA ROM, both odexed/deodexed, http://forum.xda-developers.com/showthread.php?t=2630748
you can flash a custom ROM if you would like, look at the thread in my signature it has tons of custom ROMs and kernels
Cronic2009 said:
sorry misread your previous post, those .zips are flashable through TWRP, here is a LS980 ZVA ROM, both odexed/deodexed, http://forum.xda-developers.com/showthread.php?t=2630748
you can flash a custom ROM if you would like, look at the thread in my signature it has tons of custom ROMs and kernels
Click to expand...
Click to collapse
ADB download?
Download this > http://download1983.mediafire.com/k2...loki-ls980.img
put it in your ADB folder and rename it to recovery.img ( just easier to find it )
plug the phone in
open Command Prompt in ADB folder ( hold shift + windows button in ADB folder )
fastboot flash recovery.img ( if you are using a different recovery image, sub it here, fastboot flash blank.img)
this should give you TWRP recovery, you can the use the .zips to update ROMs
CroI ic2009;518ADB12 said:
Download this > http://download1983.mediafire.com/k2...loki-ls980.img
put it in your ADB folder and rename it to recovery.img ( just easier to find it )
plug the phone in
open Command Prompt in ADB folder ( hold shift + windows button in ADB folder )
fastboot flash recovery.img ( if you are using a different recovery image, sub it here, fastboot flash blank.img)
this should give you TWRP recovery, you can the use the .zips to update ROMs
Click to expand...
Click to collapse
Where do i download adb?
ADB download here http://forum.xda-developers.com/showthread.php?t=2588979
Cronic2009 said:
ADB download here http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
One last question. How do I put ROMs onto the phone in recovery mode?I don't have any rom files for the phone at all yet. Can I flash with ADB?
eddytheyeti2 said:
One last question. How do I put ROMs onto the phone in recovery mode?I don't have any rom files for the phone at all yet. Can I flash with ADB?
Click to expand...
Click to collapse
All these things can be done through ADB yes. Didn't you have to download ADB to root in the first place? You shouldnt have to download again. However if you want to check start up a command prompt and type adb devices. That should pop up something if you have adb installed. I'm not sure if you need to be in a parent folder first though.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Demonlinx said:
All these things can be done through ADB yes. Didn't you have to download ADB to root in the first place? You shouldnt have to download again. However if you want to check start up a command prompt and type adb devices. That should pop up something if you have adb installed. I'm not sure if you need to be in a parent folder first though.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used ioroot, so no ADB. I'm also not by my laptop at all. Would the rom install command be flash fastboot **********. Zip?
eddytheyeti2 said:
I used ioroot, so no ADB. I'm also not by my laptop at all. Would the rom install comand be flash fastboot **********. Zip?
Click to expand...
Click to collapse
Not if you don't have ADB installed.
Demonlinx said:
Not if you don't have ADB installed.
Click to expand...
Click to collapse
I'm going to download ADB today.
Cronic2009 said:
ADB download here http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
So, I have ADB installed. I am on windows 8 though, and the shift+windows button are not opening the prompt. Furthermore when I plug my phone in the computer says "windows cannot find 'C:\ Program Files (X86)\Mobogenie\Mobogenie.exe'. Make sure you typed the name correctly, and then try again" I have no clue what Mobogenie is!
Advice? if there is any for me?
Edit: I can get the ADB window open, but when I type the command "fastboot flash twrp_2.6.3.3_loki-ls980"
I get the following:
unknown partition 'twrp_2.6.3.3_loki-ls980'
error: cannot determine image filename for 'twrp_2.6.3.3_loki-ls980'
I am not sure what to do... Is the Mobogenie the issue? I have all of the proper drivers installed. though I don't see my device in computer on the laptop. Help please? I don't think I can take the device into sprint or lg, because it was rooted.
I would really appreciate some help on this one... I attempted to flash the updated Mahdi Rom (09/20 build) this morning. I'm using the latest Philz Recovery if that matters. I performed the normal wipe procedure and when I went to flash the rom it told me the file was invalid. I think I might have tried to use a zip that wasn't fully downloaded.
I didn't have any other recoveries on my phone (I know... not smart) so I need to figure out how to flash a new rom without using recovery. I'm not completely hopeless and I'm willing to do what it takes to get my phone back!
Any help would be great! Thanks.
Have you tried adb? Your phone will be called sideload when you command adb devices.
Sent from my LG-D800 using Tapatalk
I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?
Rogueharvest said:
I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?
Click to expand...
Click to collapse
You can load adb on Mac. I believe there's a zip somewhere on xda with only the three files need, or download the package from Android. Place it in whatever your username folder is too make life easier. Also add ./ (dot slash) before every command.
Here's the command order for my setup.
cd Android/platform-tools
./adb devices
./adb sideload **DRAG FILE INTO TERMINAL**
Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Update: I think I figured it out. The command prompt needed to be reinitiated.
Thanks again for you help! Moments like that are always a little scary!
Rogueharvest said:
Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Click to expand...
Click to collapse
Does it recognize sideload when you type ./adb devices? If not and you're in adb on Philz unplug/replug the charger.
Having trouble finding anything for this specific model, thank you for helping!
i would love even just an older firmware file :S
magik20 said:
Having trouble finding anything for this specific model, thank you for helping!
Click to expand...
Click to collapse
You can probably root but there are no custom recoveries or ROMs for this device yet. There won't be any until a developer with the knowledge actually gets one of these devices and that probably won't happen because the REAL developers own and build for the more popular and high end devices.
You'll probably get custom recovery and ROMs quicker if you learn to build them or port them for yourself. Sad, but true.
bilalwiggles said:
i would love even just an older firmware file :S
Click to expand...
Click to collapse
Sent from my SCH-I535 using Tapatalk
Is there a root of there is plz put a link I having trouble finding a root
Please root or twrp
Sent from my SM-J320W8 using XDA Labs
Vee89 said:
Please root or twrp
Click to expand...
Click to collapse
Does this device have a locked bootloader?
Not shure
Sent from my SM-J320W8 using XDA Labs
Vee89 said:
Not shure
Sent from my SM-J320W8 using XDA Labs
Click to expand...
Click to collapse
Then do a search for:
"How to check bootloader status on android"
This will give you different methods to check.
Learn to search instead of being lazy waiting for someone to do the thinking and the work for you. If you want to do this then get off your but and get busy finding answers.
You are the one that wants to do this to your device, not us, if it's what you really want then you'll do whatever it takes, if you don't then it means you didn't really want it in the first place.
You'll get TWRP faster if you learn to port or build your own, many new members that can't find anything for their device end up building their own TWRP, it's not that complicated.
Sent from my SM-S903VL using Tapatalk
Its locked
Sent from my SM-J320W8 using XDA Labs
Vee89 said:
Its locked
Sent from my SM-J320W8 using XDA Labs
Click to expand...
Click to collapse
Then you can't use TWRP unless you get it unlocked.
Before you ask how to do that, search first for yourself how to unlock bootloader on your model number.
If it can't be unlocked then you are out of luck with using custom ROMs, there are a lot of devices that can't be unlocked or use custom ROMs. In the future, research your devices before you buy them, that way you know whether it has custom support before you buy it. Then you won't be stuck with a device that has nothing available.
Sent from my SM-S903VL using Tapatalk
Vee89 said:
Its locked
Click to expand...
Click to collapse
Do you have the stock boot image from the stock firmware?
No
Sent from my SM-J320W8 using XDA Labs
Phone rooted check here :
BR,
[email protected]
ashyx said:
Do you have the stock boot image from the stock firmware?
Click to expand...
Click to collapse
How could I get the stock image? I really would like to root my device but it seems this model is a lost cause in most cases, I softbricked my device once by using a different models IMG to root mine, but i fixed it.
DemandingZ said:
How could I get the stock image? I really would like to root my device but it seems this model is a lost cause in most cases, I softbricked my device once by using a different models IMG to root mine, but i fixed it.
Click to expand...
Click to collapse
Did you try the video posted above?
Sent from my SM-S903VL using Tapatalk
---------- Post added at 09:42 PM ---------- Previous post was at 09:22 PM ----------
[email protected] said:
Phone rooted check here :
BR,
[email protected]
Click to expand...
Click to collapse
The done supports devices,with unlocked bootloader, if this device has an unlocked bootloader then custom recovery would be the best way to root and it wouldn't cost anything or require using any potentially questionable hardware or software. That's just my opinion though.
Sent from my SM-S903VL using Tapatalk
DemandingZ said:
How could I get the stock image? I really would like to root my device but it seems this model is a lost cause in most cases, I softbricked my device once by using a different models IMG to root mine, but i fixed it.
Click to expand...
Click to collapse
I'm still waiting for a response on this
https://forum.xda-developers.com/showpost.php?p=72585838&postcount=145
It seems not all J320w8 models are equal.
I really need the boot twrp for sm-j320w8 its network is unlocked i flashed it bricked it 3 times n now its killing me that i cant please send a link n i will send 25cash paypal thank you [email protected]
magik20 said:
Having trouble finding anything for this specific model, thank you for helping!
Click to expand...
Click to collapse
I think it's possible to do it via open shell adb in cmd.exe using the specific commands .. unlock the bootloader is done with fastboot in cmd under windows or in a linux terminal.
.
ADB: (android debug bridge)
adb devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
adb reboot - restart your phone normally
adb reboot recovery - restart your phone in recovery mode
adb reboot bootloader - restart your phone in bootloader mode (fastboot)
adb shell - allows to explore the phone, knowing that Android is based on linux you need to know the linux commands
adb remount - remount the system partition of the phone, you can then read and write
adb push xxx yyy - copy the xxx file from the computer to the yyy file / folder on the phone (root rights required)
adb pull xxx yyy - copy the phone's xxx file to the yyy file / folder on the computer (root rights required)
fastboot:
fastboot devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
fastboot reboot - restarts your phone normally
fastboot oem unlock - unlocks the bootloader
fastboot erase xxx - erases the xxx partition (userdata, cache, etc ...)
fastboot flash xxx yyy - flash the xxx partition with the yyy image
DroidShell said:
I think it's possible to do it via open shell adb in cmd.exe using the specific commands .. unlock the bootloader is done with fastboot in cmd under windows or in a linux terminal.
.
ADB: (android debug bridge)
adb devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
adb reboot - restart your phone normally
adb reboot recovery - restart your phone in recovery mode
adb reboot bootloader - restart your phone in bootloader mode (fastboot)
adb shell - allows to explore the phone, knowing that Android is based on linux you need to know the linux commands
adb remount - remount the system partition of the phone, you can then read and write
adb push xxx yyy - copy the xxx file from the computer to the yyy file / folder on the phone (root rights required)
adb pull xxx yyy - copy the phone's xxx file to the yyy file / folder on the computer (root rights required)
fastboot:
fastboot devices - gives you the list of android devices connected to your pc, lets see if your phone is well recognized before doing anything
fastboot reboot - restarts your phone normally
fastboot oem unlock - unlocks the bootloader
fastboot erase xxx - erases the xxx partition (userdata, cache, etc ...)
fastboot flash xxx yyy - flash the xxx partition with the yyy image
Click to expand...
Click to collapse
Irrelevant copy and paste info for Samsung devices.