Hello all, I was messing with my build.prop to get the free book from the Play Books offer when after a reboot my device stopped booting. After the "Google" I just get a black screen. I'm trying to use the Nexus Toolkit the "Back to Stock" Tool, I can get into fastboot just fine but when the tool opens the command window I get "EOCD not found, not zip" then a bunch of nonsense characters. Took a screenshot http://i.imgur.com/FwsfgzI.jpg Any suggestions?
yea, dont use root toolkits.
flash the factory img via fastboot while youre in the bootloader. and if you want to edit your build.prop, use a root file manager, edit it, then save. reboot for it to take affect.
What he said ^^^
Try this guide,
http://forum.xda-developers.com/showthread.php?t=2513701
nameback said:
Any suggestions?
Click to expand...
Click to collapse
Stop using toolkits.
Just extract the build.prop out of the rom zip and push it with adb.
Code:
adb push build.prop /system
LOL. Simms is way ahead of me.
No suggestions for this toolkits. We don't recommend them.
Editing the build prop incorrectly will cause a boot loop. Its an easy fix. Reflash your ROM (download a ROM.zip and flash via recovery) or restore your nandroid backup that you will have taken before modifying /system
Going back to stock is a very long and noob thing to do. This is the problem with toolkits. No one understands what they're doing.
Please read through the guides here. They will help you no end. They're in my signature
oh, i messed up. first suggestion should have been just reflash your rom, dirty(no wiping) :angel:
simms22 said:
oh, i messed up. first suggestion should have been just reflash your rom, dirty(no wiping) :angel:
Click to expand...
Click to collapse
Lol Guess disregard my link too. ?
theesotericone said:
Stop using toolkits.
Just extract the build.prop out of the rom zip and push it with adb.
Code:
adb push build.prop /system
LOL. Simms is way ahead of me.
Click to expand...
Click to collapse
I'm just running stock and I've been meaning to learn how to do things properly so I'll download the SDK and give it a whirl. Thanks for the help all!
nameback said:
Stop using toolkits.
Just extract the build.prop out of the rom zip and push it with adb.
I'm just running stock and I've been meaning to learn how to do things properly so I'll download the SDK and give it a whirl. Thanks for the help all!
Click to expand...
Click to collapse
You don't need the SDK.
Click the guides link in my signature and read "adb and fastboot. What is it?"
Sorry maybe I need a little more hand holding here, how do I get adb working if I can't boot my device? It doesn't seem like you can push with fastboot.
Adb works in custom recovery or android.
Again, all covered in my thread that I asked you to read.
Tried to pm you but apparently you don't get them. Your sig has disappeared. Just a heads up. To the OP, look at the sticky in N5 q&a about adb.
Weird, you sig is in one post but not the one you told the OP to check it in.
wangdaning said:
Tried to pm you but apparently you don't get them. Your sig has disappeared. Just a heads up. To the OP, look at the sticky in N5 q&a about adb.
Weird, you sig is in one post but not the one you told the OP to check it in.
Click to expand...
Click to collapse
Ah interesting, thanks. I posted that from the XDA one alpha app.
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
Test
Related
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
when you say perm root you mean s-off right?
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
sinistersai4d4d said:
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
Click to expand...
Click to collapse
its not s-off, go here to get s-off
http://forum.xda-developers.com/showthread.php?t=1576672
my HTC MyTouch 4G Slide using Tapatalk 2
gtmaster303 said:
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Click to expand...
Click to collapse
Badass
Sent from my myTouch_4G_Slide using xda premium
Let me take advantage of this newb. I got my new device, S-On Unlocked. I restored my modded version of stock and using blues UV 5% kernel. Wifi wont work, and my camera has weird lines on it. But the pics are still good. I just needa fastboot the boot.img righ'?
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
1) This goes in General. I don't know why the mods can't just add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
blackknightavalon said:
1) This goes in General. I don't know why the mods just don't add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
Click to expand...
Click to collapse
Ok, I'm def S-ON but unlocked and nperm rooted.
Can someone walk me through what to do? How can I fastboot the rom's boot.img?
I'm sorry I'm new to this, that's why I'm using my secondary device to learn. I've been googling anything I can find and it got me to through the root process but now I'm stuck.
xmc wildchild22 said:
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Click to expand...
Click to collapse
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
sinistersai4d4d said:
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
Click to expand...
Click to collapse
Did you not read the stickies?
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Sent from my SGH-T959V using Tapatalk 2
wesomatic said:
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Click to expand...
Click to collapse
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
sinistersai4d4d said:
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
Click to expand...
Click to collapse
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
AgentCherryColla said:
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
*UPDATE*
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
sinistersai4d4d said:
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Click to expand...
Click to collapse
Of course not. 'Fastboot' is an 'ADB' command. BUT if Hasoon's tool 'can't find device'....that's an ADB error message and you probably don't have all the drivers installed that you need but he has the necessary files included for what you need for 'Unlocked" & recovering from a mess-up. You may as well go ahead & install ADB tho....you'll eventually need it.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
sinistersai4d4d said:
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
Click to expand...
Click to collapse
I believe what you did is 'Flash' a ROM from MikROMs but the kernel didn't go because you have S-On. Take that same '.zip' you just flashed, look inside it and put the file named 'boot.img' where you can find it in the windows 'path' and THEN
'fastboot flash boot boot.img' http://forum.xda-developers.com/showthread.php?t=1508556
You should boot up fine then.
i cant install no roms every rom i put in stay stuck at boot screen doesnt freeze just hangs on boot what can i do???????:crying::crying::crying:
crimedave1987 said:
i cant install no roms every rom i put in stay stuck at boot screen doesnt freeze just hangs on boot what can i do???????:crying::crying::crying:
Click to expand...
Click to collapse
are you s-on or s-off?
mattlowry said:
are you s-on or s-off?
Click to expand...
Click to collapse
s-on
crimedave1987 said:
i cant install no roms every rom i put in stay stuck at boot screen doesnt freeze just hangs on boot what can i do???????:crying::crying::crying:
Click to expand...
Click to collapse
Need more info. What ROM.....S-on, S-Off......what recovery......you know. As much of a description of what you're working with as you can think of. How are you flashing, what had you done right before this happened if anything, etc., etc......
WeekendsR2Short said:
Need more info. What ROM.....S-on, S-Off......what recovery......you know. As much of a description of what you're working with as you can think of. How are you flashing, what had you done right before this happened if anything, etc., etc......
Click to expand...
Click to collapse
i was trying to install rubix senceless 4.0 , cyanogen mod 9 , bulletproof 1.1 and i have cwm recovery 5.5.0.4 and im just flashing all thru cwm Recovery it will install okay then once i reboot bulletproof rom will hang on the t-mobile mytouch 4g slide other roms like rubix and cyanogen will hang at the boot animation screen prob i did something wrong cause when i wanted to install a new fresh rom i thought formatting everything wont damage the phone but here is what i format
on cwm-based recovery5.5.0.4
wipe data/factory reset - passed but with an error E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
wipe cache partition - passed
advanced/wipe dalvik cache wiped - passed
wipe battery stats - passed fix permissions - passed
This is why I have cwm v4.0.0.9
Sent from my myTouch 4G Slide using xda premium
K7Cobb said:
This is why I have cwm v4.0.0.9
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
ok whyy?????
will this recovery fix my problem?
crimedave1987 said:
i cant install no roms every rom i put in stay stuck at boot screen doesnt freeze just hangs on boot what can i do???????:crying::crying::crying:
Click to expand...
Click to collapse
damn this long no response is telling me i damaged my phone
crimedave1987 said:
ok whyy?????
will this recovery fix my problem?
Click to expand...
Click to collapse
Have you by any chance tried out CWM 6.0 and decided to go back to 5.5.0.4? Did you extract the "boot.img" file from the ROM & fastboot flash boot boot.img thru ADB AFTER you flashed your ROM.zip file since you are S-On?
---------- Post added at 08:22 AM ---------- Previous post was at 08:17 AM ----------
K7Cobb said:
This is why I have cwm v4.0.0.9
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
You won't be too happy with 4.0.0.9 if you ever let your phone go COMPLETLY dead. It will brick it.
WeekendsR2Short said:
Have you by any chance tried out CWM 6.0 and decided to go back to 5.5.0.4? Did you extract the "boot.img" file from the ROM & fastboot flash boot boot.img thru ADB AFTER you flashed your ROM.zip file since you are S-On?
---------- Post added at 08:22 AM ---------- Previous post was at 08:17 AM ----------
You won't be too happy with 4.0.0.9 if you ever let your phone go COMPLETLY dead. It will brick it.
Click to expand...
Click to collapse
well im using the aio toolkit by hansoon
and the latest cwm is 5.0.2.7 for mt4gs
crimedave1987 said:
well im using the aio toolkit by hansoon
and the latest cwm is 5.0.2.7 for mt4gs
Click to expand...
Click to collapse
Hasoon's toolkit is for unlocking, installing CWM & superuser if my memory serves me though. You can flash your ROMs thu recovery (CWM) but with S-On you will have to extract the "boot.img" file and flash it seperately thru ADB because HBoot will stop an unsigned file it sees as a Radio from flashing if S-On.
There ARE a couple of other versions of CWM....5.5.0.4 & 6.0.0.0. (6.0 has some REAL issues though and has bricked several phones so IF you notice it....don't USE it.)
This will explain it much better to you...... http://forum.xda-developers.com/showthread.php?t=1508556
is there anything i can do to fix this problem cause i really need the phone
okay just now i flashed cwm ver 5.0.2.7 and before when i had it i had the option (mounts and storage menu)
i formatted the cache/data/sd-ext/system is that what i did wrong?
crimedave1987 said:
is there anything i can do to fix this problem cause i really need the phone
okay just now i flashed cwm ver 5.0.2.7 and before when i had it i had the option (mounts and storage menu)
i formatted the cache/data/sd-ext/system is that what i did wrong?
Click to expand...
Click to collapse
If you flashed your ROM and then the boot image after you did that it shouldn't be a problem. Did you read the post above yours and answer those question though? Did you check the link I provided and understand fully what it was talking about? That is VERY important.
WeekendsR2Short said:
If you flashed your ROM and then the boot image after you did that it shouldn't be a problem. Did you read the post above yours and answer those question though? Did you check the link I provided and understand fully what it was talking about? That is VERY important.
Click to expand...
Click to collapse
can you explain step by step cause its not giving me details
i extracted just the boot.img from the rom put it in a new folder then copied the rom.zip file to the same new folder im not doing the command prompt right? please help sorry im a noob
crimedave1987 said:
can you explain step by step cause its not giving me details
i extracted just the boot.img from the rom put it in a new folder then copied the rom.zip file to the same new folder im not doing the command prompt right? please help sorry im a noob
Click to expand...
Click to collapse
do you have adb and fastboot setup?
http://forum.xda-developers.com/showthread.php?t=928370 - adb and fastboot the easy way
mattlowry said:
do you have adb and fastboot setup?
Click to expand...
Click to collapse
i dont think so
WeekendsR2Short said:
This will explain it much better to you...... http://forum.xda-developers.com/showthread.php?t=1508556
Click to expand...
Click to collapse
this is the step by step instructions
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
crimedave1987 said:
i dont think so
Click to expand...
Click to collapse
if you dont you need to do this ASAP because when you are on you have to fastboot .img files to make it work im not too familiar as i am s-off. follow my first link to set up adb and fastboot then go to the link weekend posted. (which is stickied in the development section).
Move your ROM.zip file to the root directory of your phone first. Then put the boot.img file in the root directory of your computer since it's already in the windows path. that's " C:\ " Since you already have Hasoon's toolkit installed we'll use that instead of putting you thru the ADB installation right now for time & simplicity's sake.
Go to Windows Explorer & navigate to the folder you have his toolkit in and copy the name of the folder down EXACTLY. Then you can pull up your command prompt window again. When it initiates it will say C:\ sumpthin....sumpthin...sumpthin. From there type CD\ and it will "change directory" back to C:\ THEN you can type cd\ "whatever you named the folder that has Hasoon's toolkit in it".
That will take you to that folder just like explorer will do. Just let it sit there for a second.
On your phone in Recovery you wipe user data/ factory reset 3 times then you can....
Wipe cache 3 times and toggle down to "Advanced"
That will take you to another screen where you will see "Dalvik Cache"
Wipe that 3 times as well.
Then hit "Go back" & return to the previous screen & select "install zip from SD card"
Once complete leave your phone sitting & still plugged in to the usb
NOW....go back to your computer and type....
reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Once your phone reboots, leave it alone for 5 minutes to let everything settle in and you should be "good to go".
WeekendsR2Short said:
Move your ROM.zip file to the root directory of your phone first. Then put the boot.img file in the root directory of your computer since it's already in the windows path. that's " C:\ " Since you already have Hasoon's toolkit installed we'll use that instead of putting you thru the ADB installation right now for time & simplicity's sake.
QUOTE]
the method for adb i posted is quick and easy. unzip to c: drive and you are done
Click to expand...
Click to collapse
mattlowry said:
this is the step by step instructions
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
if you dont you need to do this ASAP because when you are on you have to fastboot .img files to make it work im not too familiar as i am s-off. follow my first link to set up adb and fastboot then go to the link weekend posted. (which is stickied in the development section).
Click to expand...
Click to collapse
If we can do it like this the first time it may keep him from going into sensory overload. LMAO!
---------- Post added at 09:48 AM ---------- Previous post was at 09:45 AM ----------
mattlowry said:
WeekendsR2Short said:
Move your ROM.zip file to the root directory of your phone first. Then put the boot.img file in the root directory of your computer since it's already in the windows path. that's " C:\ " Since you already have Hasoon's toolkit installed we'll use that instead of putting you thru the ADB installation right now for time & simplicity's sake.
QUOTE]
the method for adb i posted is quick and easy. unzip to c: drive and you are done
Click to expand...
Click to collapse
You're right. It IS very easy. Either way should work but sometimes my mind doesn't go down the easiest path.
Try Matt's way first CrimeDave......
---------- Post added at 10:10 AM ---------- Previous post was at 09:48 AM ----------
mattlowry said:
WeekendsR2Short said:
Move your ROM.zip file to the root directory of your phone first. Then put the boot.img file in the root directory of your computer since it's already in the windows path. that's " C:\ " Since you already have Hasoon's toolkit installed we'll use that instead of putting you thru the ADB installation right now for time & simplicity's sake.
QUOTE]
the method for adb i posted is quick and easy. unzip to c: drive and you are done
Click to expand...
Click to collapse
Mattlowery....I COMPLETLY forgot about the shortcut tool for setting up ADB!! My bad.
CrimeDave, I defer to Matt's way completly. I just now followed his link. I was trying to get you around something you didn't HAVE to get around in the first place. OH well..... LOL
Sorry if I confused you.....
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Okay, so I decided to do something stupid and forget to backup my HTC One S while rooting. I installed CM10, and it got stuck in a bootloop, so stupid me decided to also do a factory reset and basically delete everything I needed to get out of it. I've tried numerous things, including ADB sideloading a ROM, but whenever I do that, it also gets stuck in a boot loop. I have no idea how to use RUU's, and if anybody could help me to fix my phone, that'd be really really helpful. I'm also kindof a n00b towards this stuff, so step-by-step instructions would be much appriciated Thanks.
~MuZiiX
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
CuzCrostyPwns said:
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
Click to expand...
Click to collapse
I think my device is s-off...i used the HTC One S all in one toolkit, and I have no idea what supercid is :s I've tried a couple RUU's before (don't know if i used them correctly, but i did relock the bootloader when i did it) but none of them helped. It just stayed at a black screen with "htc" in the middle. No error triangles or anything.
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
CuzCrostyPwns said:
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
Click to expand...
Click to collapse
Yeah, the RUU's were .exe's with my phone connected through USB. I can get into recovery, I have CWM installed.
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
CuzCrostyPwns said:
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
Click to expand...
Click to collapse
Well thats what I've been trying to do with the ADB sideloading, because it wont let me mount my sd card. It just says 'ERROR MOUNTING SD CARD" and when I've tryed flashing a new ROM from ADB sideloading, it just gets stuck in a bootloop again.
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
CuzCrostyPwns said:
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
Click to expand...
Click to collapse
I've tried running multiple RUU files, and I have no idea what one to use. The phone when I got it was unlocked, and the android version was ICS I'm pretty sure.
I dunno how to find my stock settings because I cant get past the loading screen.
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
did you flash boot.img? most of roms will bootloop without it
Roundtableprez said:
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
the boot.img is located in the zip you downloaded from get.cm
NQNH said:
the boot.img is located in the zip you downloaded from get.cm
Click to expand...
Click to collapse
So what command would I use while flashing the boot.IMG file? (again sorry for not getting this, I just wanna get my phone working again)
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Download or build from source
Download gapps
wipe unless you're upgrading from an earlier CM10 ROM
flash rom in recovery
flash gapps in recovery
unless you have s-off fastboot flash boot boot.img
Click to expand...
Click to collapse
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
dc211 said:
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
Click to expand...
Click to collapse
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
MuZiiX said:
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
Click to expand...
Click to collapse
It not really a big deal. Your problem is the most common one we see in Q&A. Also, once you finish flashing the boot.img keep in mind that CM10 can take a few minutes to boot the first time.
Also, just a heads up while the toolkits are helpful learning the command yourself actually lets do you a lot more things a lot faster.
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
CuzCrostyPwns said:
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
MuZiiX said:
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
Click to expand...
Click to collapse
Nope, just gotta do it one of the three ways mentioned. If debugging isn't enabled use option 1.
This can either be done via
1 powering off and keeping volume up & the power-button pressed
2 the extended power-menu (If your ROM has it, just select "reboot" & then "bootloader")
3 via adb, connect your phone with the pc, make sure it says "USB debugging connected", go to Android/platform-tools/ & then press shift while you perform a right click with the mouse, then choose "open prompt here", type
Click to expand...
Click to collapse
I am far from a developer but I pulled the stock kernel for JSS15J, decompiled it and under "default.prop" edit
Code:
ro.secure=1 to ro.secure=0
and
Code:
ro.adb.secure=1 to ro.adb.secure=0
(probably super unsafe)
Recompiled and this booted just fine on my N7(2013), although size did change dramatically?
Anyway, didn't do any other wizardry, as I really don't know any. Hence, why I am attaching the stock kernel as well for actual wizards to perform on.
Stock and Insecure.zip This is hosted on Mega
Full /system /boot and /recovery: http://forum.xda-developers.com/showthread.php?t=2381438
Can you upload system.img too
Yeah, please upload the system.img, I am very curious about it Have a nice day.
nutzu4ever said:
Yeah, please upload the system.img, I am very curious about it Have a nice day.
Click to expand...
Click to collapse
Here you go
CLICK HERE
Credit to Nburnes
phuduong said:
Here you go
CLICK HERE
Credit to Nburnes
Click to expand...
Click to collapse
That's really helpful. Could you also pull the stock recovery if you still have it? The one that's floating around on xda is TWRP masquerading as stock.
dexgen said:
That's really helpful. Could you also pull the stock recovery if you still have it? The one that's floating around on xda is TWRP masquerading as stock.
Click to expand...
Click to collapse
If you tell me what to do, I'll pull the stock recovery for you.
gksmithlcw said:
If you tell me what to do, I'll pull the stock recovery for you.
Click to expand...
Click to collapse
I'm no expert but I think you'd find it here:
/dev/block/platform/msm_sdcc.1/by-name/recovery
But only if you haven't flashed any other recovery.
dexgen said:
I'm no expert but I think you'd find it here:
/dev/block/platform/msm_sdcc.1/by-name/recovery
But only if you haven't flashed any other recovery.
Click to expand...
Click to collapse
Hmm... Pulled up ADB Shell and ls'd that directory and just got an echo of the path back. Tried an ADB pull for the hell of it and got an error stating it remote object was not a file or directory.
gksmithlcw said:
Hmm... Pulled up ADB Shell and ls'd that directory and just got an echo of the path back. Tried an ADB pull for the hell of it and got an error stating it remote object was not a file or directory.
Click to expand...
Click to collapse
You can take a look at this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, can you just check to see if you have /system/recovery.img on your device? It might be the fastest way.
dexgen said:
You can take a look at this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, can you just check to see if you have /system/recovery.img on your device? It might be the fastest way.
Click to expand...
Click to collapse
No recovery.img in the ls of /system; I have recovery-from-boot.p. I'll check the link.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
dexgen said:
You can take a look at this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, can you just check to see if you have /system/recovery.img on your device? It might be the fastest way.
Click to expand...
Click to collapse
It looks like I need root to do this and, of course, to gain root I have to flash a custom recovery SO I think we're out of luck until Google posts factory images.
If anyone knows how to do it without root, I'll gladly try it.
gksmithlcw said:
No recovery.img in the ls of /system; I have recovery-from-boot.p. I'll check the link.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
It looks like I need root to do this and, of course, to gain root I have to flash a custom recovery SO I think we're out of luck until Google posts factory images.
If anyone knows how to do it without root, I'll gladly try it.
Click to expand...
Click to collapse
Just an FYI that you can access the stock recovery after rooting. The 'file' you mentioned: "recovery-from-boot.p" causes your custom recovery to revert back to stock after a reboot. If you've rooted a Nexus you may recall that one of the first steps is to change that file to "recovery-from-boot.p.bak" (or similar) so that your system will retain the custom recovery. My point is that you can root with TWRP or CWM, reboot and you'll revert back to the stock recovery. (You don't lose root, just the custom recovery). Pull the stock recovery.img and then flash your preferred custom recovery again. The 2nd time you'll want to change the file to "recovery-from-boot.p.bak" so that you don't revert back to stock again. Make Sense?
swest6602 said:
Just an FYI that you can access the stock recovery after rooting. The 'file' you mentioned: "recovery-from-boot.p" causes your custom recovery to revert back to stock after a reboot. If you've rooted a Nexus you may recall that one of the first steps is to change that file to "recovery-from-boot.p.bak" (or similar) so that your system will retain the custom recovery. My point is that you can root with TWRP or CWM, reboot and you'll revert back to the stock recovery. (You don't lose root, just the custom recovery). Pull the stock recovery.img and then flash your preferred custom recovery again. The 2nd time you'll want to change the file to "recovery-from-boot.p.bak" so that you don't revert back to stock again. Make Sense?
Click to expand...
Click to collapse
It's been awhile since I unlocked my G-Nex and rooted it but I do recall this. I'm hoping CWM for the new N7 shows up quickly.
gksmithlcw said:
It's been awhile since I unlocked my G-Nex and rooted it but I do recall this. I'm hoping CWM for the new N7 shows up quickly.
Click to expand...
Click to collapse
TWRP is out. I haven't tried it, but there is a How To started in General and there is a download link.
Sent from my Nexus 7 using Tapatalk HD
swest6602 said:
TWRP is out. I haven't tried it, but there is a How To started in General and there is a download link.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Oh, I know. I'd rather wait for CWM Touch. Thanks for the link though.
gksmithlcw said:
Oh, I know. I'd rather wait for CWM Touch. Thanks for the link though.
Click to expand...
Click to collapse
Did you see this link: http://forum.xda-developers.com/showthread.php?t=2381544
Brenex said:
Did you see this link: http://forum.xda-developers.com/showthread.php?t=2381544
Click to expand...
Click to collapse
I did, thank you!
Brenex said:
Did you see this link: http://forum.xda-developers.com/showthread.php?t=2381544
Click to expand...
Click to collapse
Flashed CWM through fastboot working fine. I prefer CWM myself. Thanks!
You can also just BOOT into recovery w/o flashing it (fastboot boot recovery <blah.img>. I did this with TWRP and backed up the device's system/boot/recovery.
I assume that would have backed up the original recovery right?
What does insecure means for a kernel?
Sent from my Nexus 7 using Tapatalk 4 Beta
casonswag said:
What does insecure means for a kernel?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It allows ADB to run as root on the devices.
This is really a useful feature for Developers because it allows simplier access to the file system... For Example...
With an unsecure image you can do... "ADB Pulls" and pull files from the /data/ partition on the device (I forget if you can do that or not on a secure image)
But you can also do ADB push which to me is essential because I may be working on, lets say, a custom battery mod or a customer XXXXXXX. And instead of putting it in a flashable zip and flashing it each time I can use an "ADB push" command to push the file where I want it.
Unsecure may not do much for average Joe building ROMS but this is quintessential for developers.
Got it? Good!
I'm wondering if it's possible to root my phone, install an app that's required to be installed as system then unroot my phone back to normal?
I'm on the latest stable miui 8.5.2.0. I'd like to install the new pixel launcher and have Google now working which requires the APK to be installed as a system app.
Require unrooted phone for work/banking apps.
Easier way: copy the apk to /system/app/ in twrp. When you reboot, it should be installed as a system app.
theOriginalSuperl2 said:
Easier way: copy the apk to /system/app/ in twrp. When you reboot, it should be installed as a system app.
Click to expand...
Click to collapse
Oh cool I never knew about that way. But I don't have TWRP installed. It took me forever to get the vendor ROM off my Xiaomi phone and get back to stock.
Are you saying I should install TWRP and then unroot?
umirza85 said:
Oh cool I never knew about that way. But I don't have TWRP installed. It took me forever to get the vendor ROM off my Xiaomi phone and get back to stock.
Are you saying I should install TWRP and then unroot?
Click to expand...
Click to collapse
If you install TWRP, and copy the APK, then it won't root your phone at all. You can re-flash the stock recovery after, if you want.
theOriginalSuperl2 said:
If you install TWRP, and copy the APK, then it won't root your phone at all. You can re-flash the stock recovery after, if you want.
Click to expand...
Click to collapse
Oh thats so awesome! I believe I read somewhere that you need the stock recovery in order to do OTA updates, so that would definitely be preferable.
Thanks so much for taking the time to reply. One more question, is there a guide anywhere on how to put the stock recovery back onto the Mi 5s Plus?
umirza85 said:
Oh thats so awesome! I believe I read somewhere that you need the stock recovery in order to do OTA updates, so that would definitely be preferable.
Thanks so much for taking the time to reply. One more question, is there a guide anywhere on how to put the stock recovery back onto the Mi 5s Plus?
Click to expand...
Click to collapse
I don't think so, but all you need to do is flash a stock recovery image with fastboot. You have to find one online.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
theOriginalSuperl2 said:
I don't think so, but all you need to do is flash a stock recovery image with fastboot. You have to find one online.
Click to expand...
Click to collapse
Hang on. There's a much easier way, and I can't find the images online. I'll post how soon, have to go for now.
theOriginalSuperl2 said:
I don't think so, but all you need to do is flash a stock recovery image with fastboot. You have to find one online.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
Hang on. There's a much easier way, and I can't find the images online. I'll post how soon, have to go for now.
Click to expand...
Click to collapse
Thats great thanks! Appreciate it.
umirza85 said:
Thats great thanks! Appreciate it.
Click to expand...
Click to collapse
You actually don't need to flash TWRP at all.
1: Download TWRP on your computer.
2: Make sure you have the APK on your phone.
3: Run the command "fastboot boot twrp.img" in fastboot mode, where twrp.img is the TWRP filename. On Linux, this may need to be run as root. This command will temporarily boot TWRP, without flashing it.
4: Copy your APK to /system/app/
5: Reboot into android. The app should be installed.
I'm curious why you need to install an app as a system app?
theOriginalSuperl2 said:
You actually don't need to flash TWRP at all.
1: Download TWRP on your computer.
2: Make sure you have the APK on your phone.
3: Run the command "fastboot boot twrp.img" in fastboot mode, where twrp.img is the TWRP filename. On Linux, this may need to be run as root. This command will temporarily boot TWRP, without flashing it.
4: Copy your APK to /system/app/
5: Reboot into android. The app should be installed.
I'm curious why you need to install an app as a system app?
Click to expand...
Click to collapse
Whoa!! no way! That is so much easier and dont have to mess about with trying to but the phone back to stock after. Youre the best!
I want to use the new pixel 2 launcher, and for all the functionality to work (i.e google now integration) the app needs to be installed as a system app!
This was make it so simple to try it out without making any permanent changes. Thanks again!
umirza85 said:
Whoa!! no way! That is so much easier and dont have to mess about with trying to but the phone back to stock after. Youre the best!
I want to use the new pixel 2 launcher, and for all the functionality to work (i.e google now integration) the app needs to be installed as a system app!
This was make it so simple to try it out without making any permanent changes. Thanks again!
Click to expand...
Click to collapse
I guessed it was to use the pixel launcher. You could get a modded version instead of installing in the system, though.
I tried out the launcher too, but it was really buggy and laggy for me.
theOriginalSuperl2 said:
I guessed it was to use the pixel launcher. You could get a modded version instead of installing in the system, though.
I tried out the launcher too, but it was really buggy and laggy for me.
Click to expand...
Click to collapse
Yeah I've tried out the modded version and sucks that the google now functionality doesnt work, and as you said its quite buggy. Read in a few places that installing as system really helps, and with your method it seems we can try it out without switching my phone off of being completely stock (also forgot to mention that I need stock recovery to properly use the phone encryption feature as required by my company policy).