Related
I'm using CM7 ALpha2, so i use 1-click CWM to recover stock recovery, and i reboot it! After that i receive endless bootloop! So i try to 8 times factory reset but it doesn't work! However it can boot into CWM from sdcard, and i flash another rom , but it still have bootloop! I try all roms i have but it still bootloop ! So Please help me !
Anyone help me please? I tried my best!
Check the checksum of the CM7_NT_Alpha12_Public1.zip on your uSD to see if it matches. Many time, the fault lies in corrupted file getting flashed. Cheap uSD reader from China can corrupt your file during transfer. I've had this experience and heard of it. Use a good uSD reader and always check the checksum.
You can shutdown your NT by holding the power button until it shut of. Re-download CM7_NT_Alpha12_Public1.zip and re-flash.
succulent said:
Check the checksum of the CM7_NT_Alpha12_Public1.zip on your uSD to see if it matches. Many time, the fault lies in corrupted file getting flashed. Cheap uSD reader from China can corrupt your file during transfer. I've had this experience and heard of it. Use a good uSD reader and always check the checksum.
You can shutdown your NT by holding the power button until it shut of. Re-download CM7_NT_Alpha12_Public1.zip and re-flash.
Click to expand...
Click to collapse
Not only CM7 Alpha2, i tried all rom in forum, none of them worked !
From recovery, do a complete data wipe (-wipe data/factory reset)
then wipe your cache (-wipe cache partition)
Install an md5 verified zip of CM7.
Wipe cache partition again. Reboot
See if that works.
During CM7 testing, the only time we encountered boot loops was from not doing a cache wipe. If you have installed numerous files, chances are stuff is getting corrupted.
Know-Fear said:
From recovery, do a complete data wipe (-wipe data/factory reset)
then wipe your cache (-wipe cache partition)
Install an md5 verified zip of CM7.
Wipe cache partition again. Reboot
See if that works.
During CM7 testing, the only time we encountered boot loops was from not doing a cache wipe. If you have installed numerous files, chances are stuff is getting corrupted.
Click to expand...
Click to collapse
It still not work , it still bootloop ! !
blackhat007 said:
It still not work , it still bootloop ! !
Click to expand...
Click to collapse
Try the cwm fix by indirect to push cwm image again back in place , you may want to do all the wipes data, cache, advanced> dalvik cache and system partition just in case but DO NOT format any other partition or you'll mess your device even more.
~ Veronica
Sent from XDA premium using my Nook Tablet
lavero.burgos said:
Try the cwm fix by indirect to push cwm image again back in place , you may want to do all the wipes data, cache, advanced> dalvik cache and system partition just in case but DO NOT format any other partition or you'll mess your device even more.
~ Veronica
Sent from XDA premium using my Nook Tablet
Click to expand...
Click to collapse
Yesterday when I tried to fixed this problem, perhaps I formated the /system and the /bootdata partition! Is this cause my problem
When you boot into CWM recovery, go to advanced and show log. Do you have any errors listed there?
failed to open /sys/class/android_usb/android0/state: no such file or directory
Sometimes if i unplug cable and press power button, the N screen appear one time and turn off after that, but if i plug into computer, it will become bootloop !
Is there any ideas, i dont want to send back for warranty because i'm in Viet Nam !
If you don't have ADB set up, go download Indirect's nook&zergy file. It has ADB included in it, and you will need to grab the drivers from that same post. Located here
Then you will need to follow the instructions Here
Once you have working ADB, and you copy the parted file to your sdcard do this: (not listed as such in Celtic's post)
adb devices (make sure you are detected)
adb shell (this will return a # prompt)
cd /sdcard
parted /dev/block/mmcblk0 print
answer yes and fix as many times as necessary. Eventually it will return a partition break down.
From there, clear cache again to be safe, then reboot
I was in the situation where my Nook would boot, showed the "cardboard box", and then blackness. I just took it to the B&N store hoping for a reformat. Instead they gave me a whole new NT. YMMV of course. Good luck!
Dobabobalina said:
I was in the situation where my Nook would bot, shoe the "cardboard box", and then blackness. I just took it to the B&N store hoping for a reformat. Instead they gave me a whole new NT. YMMV of course. Good luck!
Click to expand...
Click to collapse
I don't think he would have the same experience being in Vietnam.
Know-Fear said:
If you don't have ADB set up, go download Indirect's nook&zergy file. It has ADB included in it, and you will need to grab the drivers from that same post. Located here
Then you will need to follow the instructions Here
Once you have working ADB, and you copy the parted file to your sdcard do this: (not listed as such in Celtic's post)
adb devices (make sure you are detected)
adb shell (this will return a # prompt)
cd /sdcard
parted /dev/block/mmcblk0 print
answer yes and fix as many times as necessary. Eventually it will return a partition break down.
From there, clear cache again to be safe, then reboot
Click to expand...
Click to collapse
I do following the instruction but i don't understand how to :
"ADB into your device and run the binary with the following command (you'll need it to be the accesible path or you can just be in the directory where it is)"
I double click on adb.exe but nothing happend !
you must have adb set up and working on your computer. Plug your NT USB cable in to the PC. If you have this:
Open a command window from the folder your adb.exe is located. (assuming you are running windows, linux would have a totally different set up that you would need to research). If in windows, navigate to the folder your adb is in (if you followed the guide in Indirect's thread, it would be in your c:\NTROOT folder. Either way, once you are in that folder, hold down your shift key and right click and select the 'open a command window here option from the menu.
Once you have a command window open, type the following:
adb devices (again, to make sure you are being detected)
adb shell
cd /sdcard
parted /dev/block/mmcblk0 print
answer the prompts with yes and fix as directed.
Know-Fear said:
you must have adb set up and working on your computer. Plug your NT USB cable in to the PC. If you have this:
Open a command window from the folder your adb.exe is located. (assuming you are running windows, linux would have a totally different set up that you would need to research). If in windows, navigate to the folder your adb is in (if you followed the guide in Indirect's thread, it would be in your c:\NTROOT folder. Either way, once you are in that folder, hold down your shift key and right click and select the 'open a command window here option from the menu.
Once you have a command window open, type the following:
adb devices (again, to make sure you are being detected)
adb shell
cd /sdcard
parted /dev/block/mmcblk0 print
answer the prompts with yes and fix as directed.
Click to expand...
Click to collapse
I'm using win7 ultimate 64bit , i open but nothing happened! I open task manager and see process adb.exe ! I tried it in winxp sp3 so it didn't work too !
adb is ran from a command window. its not a GUI based program. Follow the instructions I have given you and you should be good to go.
This same error happened to me earlier this afternoon and was easily recovered from.
blackhat007 said:
I'm using win7 ultimate 64bit , i open but nothing happened! I open task manager and see process adb.exe ! I tried it in winxp sp3 so it didn't work too !
Click to expand...
Click to collapse
[HOW-TO] Use ADB tool | Android Debug Bridge
you cant just type adb devices and expect it to work unless you add adb to windows PATH, first you have to "cd" to the path where adb files are located, most likely C:\ntoot or wherever you have placed them, more specific info is in the tutorial i posted.
~ Veronica
Know-Fear said:
adb is ran from a command window. its not a GUI based program. Follow the instructions I have given you and you should be good to go.
This same error happened to me earlier this afternoon and was easily recovered from.
Click to expand...
Click to collapse
I understand and i run the command but it didn't recognize my devices !
List of devices attached
blackhat007 said:
I understand and i run the command but it didn't recognize my devices !
List of devices attached
Click to expand...
Click to collapse
if you never rooted using a pc but the sdcard method then you need to run the runmefirst.bat that will create a .Android folder with adb_usb.ini containing nook vendor's id needed by adb to recognize your device.
~ Veronica
I used root explorer, made a copy of my original and named it original, then copied over another build.prop from my SGSII to play with MC3 and now the prime wont boot.
Im sure I will have to wait until i get home to use my USB cable but is this something I can fix through ADB?
how can i get the Prime into state that ADB can talk to it since now all i get is a black screen after the Eee pad splash screen?
Can you get into the recovery?
yes but it it shows the little android on his back with a red triangle.
is that because im rooted?
see if you can get adb access, if so push back an original build.prop...
note... never ever push a build.prop from a different device.. its the most stupid thing you can do.
yes i feel extremely stupid. i hope i didnt brick my prime doing something this retarded.
nextelbuddy said:
yes i feel extremely stupid. i hope i didnt brick my prime doing something this retarded.
Click to expand...
Click to collapse
i hope so to bro, although i did read someone messed up his build.prop before on his prime, dunno how that went afterwards... u might need to search for that
If you have access to either adb.. or maybe if you can flash zip files from your recovery you're good to go.
Using Adb:
Running "adb devices" should print your Device #, if it prints nothing, it won't work..
adb pull /system/build.prop build.prop.bootloop
adb pull /system/original.build.prop original.build.prop (>> Edited to original.build.prop as per your last post)
Then if you look at the files on your PC..
build.prop.bootloop would be the one you have right now that's causing loops
build.prop would be your backed up working build.prop.original
Then just push the good one:
adb push original.build.prop /system/build.prop
adb pull/push usage:
adb pull remotefile localfile
adb push localfile remotefile
You may be able to go this route and reflash the entire rom if you dont have adb access. From what I understand is you rename the update.zip file to whatever it says in the link to rename to and put on the root of sd card and do the power + volume and go into recovery.
http://forum.xda-developers.com/showthread.php?t=1492887&page=18
the latest asus update can be found here.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
thank you very much i will get to work on this when i get home with my cable. i was just about to post where can i get another one but you posted directions on how to pull my copy that i created which i renamed original.build.prop
Also might wanna take a look at this thread
http://forum.xda-developers.com/showthread.php?t=1514088
PM_mobile said:
If you have access to either adb.. or maybe if you can flash zip files from your recovery you're good to go.
Using Adb:
Running "adb devices" should print your Device #, if it prints nothing, it won't work..
adb pull /system/build.prop build.prop.bootloop
adb pull /system/original.build.prop original.build.prop (>> Edited to original.build.prop as per your last post)
Then if you look at the files on your PC..
build.prop.bootloop would be the one you have right now that's causing loops
build.prop would be your backed up working build.prop.original
Then just push the good one:
adb push original.build.prop /system/build.prop
adb pull/push usage:
adb pull remotefile localfile
adb push localfile remotefile
Click to expand...
Click to collapse
i can get the device into APX mode because i installed the APX driver and when i hold VOl UP and Power, my windows 7 computer shows Asus Prime APX under System Devices and it goes away if i unplug it and vice versa plugging it back in however ABD stil shows Blank for connected devices.
not sure what Im doing wrong so im uninstalling my OLD SDK from last year and reinstalling the latest SDK to see if that helps.
ok so my Prime boots into APX mode according to windows 7 Device manager. it shows APX not greyed out.
however despite this, in CMD when i type ADB Devices it shows BLANK and of course any adb commands return no device found.
if i let the Prime reboot into its Boot loop, then ADB Composite appears in Device manager.
if i go to CMD and type ADB Devices, it always says ADB Server out of date killing server and then it shows Daemon starting and then says Failed.
if i try 2 times back to back i eventually get the Device Serial number.
so then i try PULL command and that works no problem
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
nextelbuddy said:
ok so my Prime boots into APX mode according to windows 7 Device manager. it shows APX not greyed out.
however despite this, in CMD when i type ADB Devices it shows BLANK and of course any adb commands return no device found.
if i let the Prime reboot into its Boot loop, then ADB Composite appears in Device manager.
if i go to CMD and type ADB Devices, it always says ADB Server out of date killing server and then it shows Daemon starting and then says Failed.
if i try 2 times back to back i eventually get the Device Serial number.
so then i try PULL command and that works no problem
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
Click to expand...
Click to collapse
I think its bricked... because from the research Swift and I did on a battery mod, he tried a mod I don't remember what and it ended up in boot loop. ADB won't work because of the boot loop it doesn't stay long enough in a booted state for ADB to send/receive the commands. If your still in your return period try for exchange.
nextelbuddy said:
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
Click to expand...
Click to collapse
The file system will be read only by default. You need to remount /system as read/wrire.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk
Had the same problem back then.
I did a search on the problem at the forum and found this:
"I did this and that worked for me : http://forum.xda-developers.com/show...4&postcount=21"
You need a micro sd and rename a file, easy, poof, fixed.
As far as adb goes
adb remount
or
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
foxmeister said:
The file system will be read only by default. You need to remount /system as read/write.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Unfortunately i can not remount the system. if i try to remount it says either device not found or error it can not.
its like it never listens long enough..
for example if i type ADB Devices, it will say "ADB Server out of date killing server and then it shows Daemon starting and then says Failed"
if i try that 2-3 times then it will eventually say Devices and list my Serial number.
if i try immediately after that to go to ADB SHELL, it starts and then i type:
adb push original.build.prop /system/build.prop
as soon as i hit enter it says Device not found.
even if i try that command 5 times in a row hoping that it takes one of the times, it does not.
Brollie said:
Had the same problem back then.
I did a search on the problem at the forum and found this:
"I did this and that worked for me : http://forum.xda-developers.com/show...4&postcount=21"
You need a micro sd and rename a file, easy, poof, fixed.
Click to expand...
Click to collapse
i cant look at that link, its truncated. can you post the full link please?
i tried downloading the .15 firmware from Asus site and pasting it on a micro SD card and putting it in the Prime and then booting into recovery mode but it always shows the android laying down with a red triangle.
PM_mobile said:
As far as adb goes
adb remount
or
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
i cant remount, i can shell but if i do that then it says no devices connected.
wow, i royally screwed things up with this stupid build.prop like an idiot.
For the record, once in adb shell it's not adb push anymore..
That'd be
cp /system/original.build.prop /system/build.prop
I doubt this will do you any good, it seems you just can't stay in adb long enough because it reboots.
You don't gave a working custom recovery do you? (like clockwork mod)
I think I've seen people with custom recoveries on their primes.. that'd allow you to adb properly or flash a zip file with your build.prop..
Also, Did you look at this thread?
http://forum.xda-developers.com/showthread.php?t=1514088
They have a few unbrick solutions and something about getting adb to work from recovery. Recovery wouldn't bootloop while you're trying to adb..
aznmode said:
You may be able to go this route and reflash the entire rom if you dont have adb access. From what I understand is you rename the update.zip file to whatever it says in the link to rename to and put on the root of sd card and do the power + volume and go into recovery.
http://forum.xda-developers.com/showthread.php?t=1492887&page=18
the latest asus update can be found here.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
Click to expand...
Click to collapse
THIS!!!
i downloaded the latest stock firmware .15 from asus support site. renamed it to
EP201_SDUPDATE.zip and copied to a micdro SD card.
held VOL DOWN + Power and when i saw the white text hit VOL UP twice
and the recovery manager detected the file on the SD card and started flashing.
no more RED triangle android anymore.
im sooo excited this worked and will definitely take more caution in regards to the build.prop file. never realized how much of an integral role it played in the android OS.
thank you very much for all your help and to the others thanks for your help with ADB. even though it didnt work, i played with ADB so much last night and today that i feel much more comfortable with it.
The screen is black and doesn't operate when you touch it.
I know you can get into the files using the recovery ...but I don't know how many volume ups and downs you need to get into it?
I am running the 5.0 JB CM10 recovery.
Volume up + volume down + power button if froyo bootloader
Volume down + power button if gingerbread bootloader
Sent from my SGH-T959 using xda app-developers app
What he is asking is, since he can't see the screen, he needs to know exactly the number of up or down spaces to get to.....
And this brings my question, where are you trying to get to in recovery?
I approve this message.
samsgun357 said:
What he is asking is, since he can't see the screen, he needs to know exactly the number of up or down spaces to get to.....
And this brings my question, where are you trying to get to in recovery?
I approve this message.
Click to expand...
Click to collapse
The option to mount USB storage....I don't think it has it anymore...I don't have It on my gs3
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
If its the same as the recovery in PA, semaphore
Its down 6, power
Up 2
I approve this message.
If you want to copy all your files from the internal storage using ADB: Reboot into CWM and connect it to your PC. In the command prompt, type:
adb shell
mount /dev/block/mmcblk0p1
(that's the partition of the internal storage in my vibrant)
exit
adb pull /sdcard C:\backup
(make sure you create the C:\backup folder first, it will begin to copy everything from your phone's storage to your harddrive)
-----
Optional: Once you are in adb shell, you can type this:
cat /etc/fstab (it will tell you the location of each partition that you can mount)
cd /sdcard (go to /sdcard partition)
ls -la (display all files in current directory)
Just remember to use 'adb pull' or 'adb push' you need to exit adb shell first.
Or just:
1. Pull battery
2. Attempt to get into recovery by guessing.
3. Adb shell Into device.
3.b if adb can't find device, go back to 1
4. Adb pull /storage/sdcard0/ or adb pull /sdcard/
It will be in the folder containing the adb file.
Sent from my GT-I9000 using xda premium
that /storage directory is new thing in Jelly Bean, I guess it does make things easier for people, instead of /sdcard and /emmc. It's a symbolic link, I don't even see it in adb shell.
The CWM doesn't auto mount the internal storage, so you still have to mount it first.
VeryCoolAlan said:
The option to mount USB storage....I don't think it has it anymore...I don't have It on my gs3
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
Maybe your GS3 uses MTP rather than mass storage.
Try: Up, Up, Down, Down, Left, Right, Left, Right, B, A, B, A
Sorry couldnt resist :laugh:
Lol, forgot select start!
I approve this message.
FaultException said:
Maybe your GS3 uses MTP rather than mass storage.
Click to expand...
Click to collapse
Probably.... I'm on CM10 .
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Thanks mate! You just saved my day.
I had the exact same problem and couldn't get sideload to work in TWRP 2.7.0.0 on Nexus5. But simple "adb push..." worked.
this doesn't work
thank you very much, you saved my day,too.
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
Thanks man... you just saved me a ton of trouble. Tried this on the Nexus 4 and works like a charm! :good:
just wanted to say thanks!
for some odd reason, my twrp (even though its the latest for my nexus7 grouper) had the same flashing no status error)
used the kill, usb, and push commands to copy over 3 different zips (rom,kernel,gapps) and it all copied over ready to flash
thanks!
23468
seriously thanks mate! work like charm :good::good:
for me it copies the small files but my rom is 1gb plus it gives me the error 'protocol failure' can some one give me a helping hand here?
please?
Same Issue
jacktackle said:
for me it copies the small files but my rom is 1gb plus it gives me the error 'protocol failure' can some one give me a helping hand here?
please?
Click to expand...
Click to collapse
Three days and All I can do is flash a recovery. Insertcoint goes though and says it's installed but nothing but HTC Screen
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
Thanks man. You're lifesaver
Awesome, this worked for me too
HELP
I have htc one s somthing wrong happend turned the storage from 16 giga into 48 mega byts i cant get back my storage what to do please help me* i still can push roms but i cant because there is no storage what to do
mahmoud hakim said:
I have htc one s somthing wrong happend turned the storage from 16 giga into 48 mega byts i cant get back my storage what to do please help me* i still can push roms but i cant because there is no storage what to do
Click to expand...
Click to collapse
Can you ruu. Then do a factory restore. That should reset the partition
This does not work for me. Firstly, I tried installing Cyanogenmod by putting it on my internal SD card, then booting to recovery and installing the zip, and this did not work. So I tried to sideload it and got the error " * failed to write data 'protocol fault (no status)' * ". I don't know what to do. I've also tried the same with Paranoid Android but I get the same errors. Any help would be greatly appreciated.
derekokelly said:
This does not work for me. Firstly, I tried installing Cyanogenmod by putting it on my internal SD card, then booting to recovery and installing the zip, and this did not work. So I tried to sideload it and got the error " * failed to write data 'protocol fault (no status)' * ". I don't know what to do. I've also tried the same with Paranoid Android but I get the same errors. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Exact same problem I have, any suggestions?
try changing to usb 2.0, usb 3.0 sometimes not working with adb command.
much love
Thanks for saving the day voxigenboy!!! I love you man. lol
And for those that simply can't get their stupid computer to recognize the LG drivers... PDANet wins with whatever voodoo they freaking use!
Thanks for your help, rescued my evening!
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
I'm sorry, that's a bit confusing.
So are u suggesting to "sideload" by:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)?
Waiting for your response.
Zenfone 5 a501cg (India) (WW)
Stock Recovery
This didn't work for me but I found this other way of passing the archive to my phone :
https://www.youtube.com/watch?v=Z3SpI7m7mFI
Okay, basically I used Teamwin and superuser to root my Dell Streak 7 with this tutorial:
watch?v=u302zKspk2E
^put the YouTube url before this, apparently I have to make 10 posts before posting links (THANKS A LOT)
It worked, but now I have a serious problem. When I open the command prompt and everything, I type adb devices and there's no problem, the device is detected and all is good. But after typing
adb shell
$su
#
when I type:
#adb devices
Error: device not found
I'm trying to make /system writable long enough to add my own files in, but I can't do that without superuser mode!
Anyone have a problem like this?
Specs: Windows 8 64-bit on a Dell Streak 7 [Teamwin + Superuser]
HackAttack37 said:
Okay, basically I used Teamwin and superuser to root my Dell Streak 7 with this tutorial:
watch?v=u302zKspk2E
^put the YouTube url before this, apparently I have to make 10 posts before posting links (THANKS A LOT)
It worked, but now I have a serious problem. When I open the command prompt and everything, I type adb devices and there's no problem, the device is detected and all is good. But after typing
adb shell
$su
#
when I type:
#adb devices
Error: device not found
I'm trying to make /system writable long enough to add my own files in, but I can't do that without superuser mode!
Anyone have a problem like this?
Specs: Windows 8 64-bit on a Dell Streak 7 [Teamwin + Superuser]
Click to expand...
Click to collapse
It detects your device in adb. When you are in adb shell, that is the same as running a Terminal app on the phone. It's not going to see an adb device because it IS the device. Just skip the adb devices while in shell and continue.
es0tericcha0s said:
It detects your device in adb. When you are in adb shell, that is the same as running a Terminal app on the phone. It's not going to see an adb device because it IS the device. Just skip the adb devices while in shell and continue.
Click to expand...
Click to collapse
Okay, so just typing "sysrw" should work for making the system writable once in adb shell su?
Have to mount the system with this command in adb shell:
mount -t yaffs2 /dev/block/mtdblock6 /system
What exactly are you trying to do? Seems like it might be easier with a file explorer that has root access. With that you can mount the system, copy stuff in, change the permissions and reboot. Works for a lot of things on most devices, but depends on the ultimate goal.
HackAttack37 said:
Okay, so just typing "sysrw" should work for making the system writable once in adb shell su?
Click to expand...
Click to collapse
mind the guy above. When you are at the # prompt. You use this code to remount /system, (you should have busybox installed).
Code:
busybox mount -o remount,rw /system
Lgrootnoob said:
mind the guy above. When you are at the # prompt. You use this code to remount /system, (you should have busybox installed).
Code:
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
The command I posted is specifically for the Dell Streak 7 from their forums. The generic one might work, but I always find specific answers to be best.
es0tericcha0s said:
The command I posted is specifically for the Dell Streak 7 from their forums. The generic one might work, but I always find specific answers to be best.
Click to expand...
Click to collapse
Alright, fair enough.