this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
I have read and tried everything
I attempted the adb method but can't get into fastboot... I believe I got the adb commands correct and I don't get an error but my the restore is not taking... at the reboot it goes right back into CWM 3.0.2.0 here's my adb shell read out...
C:\android\platform-tools>adb shell
~ #
C:\android\platform-tools>adb shell
~ # flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
usage: flash_image partition file.img
~ # flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
usage: flash_image partition file.img
~ #
I don't know what else to do, I can't find a thread that stays on track long enough to follow this issue all the way thru... please help... I have read and tried everything, i can't find a clear set of alternatives... am i missing a step?
ya, i'm stuck in the same situation. I either get a "error -1" or it says "usage: flash_image partition file.img"
does getting "usage: flash_image partition file.img" mean the file was successfully flashed?
dfspot said:
I attempted the adb method but can't get into fastboot... I believe I got the adb commands correct and I don't get an error but my the restore is not taking... at the reboot it goes right back into CWM 3.0.2.0 here's my adb shell read out...
C:\android\platform-tools>adb shell
~ #
C:\android\platform-tools>adb shell
~ # flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p2/sdcard/boot_orig.img
usage: flash_image partition file.img
~ # flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
flash_image /dev/block/mmcblk3p1/sdcard/recovery_orig.img
usage: flash_image partition file.img
~ #
I don't know what else to do, I can't find a thread that stays on track long enough to follow this issue all the way thru... please help... I have read and tried everything, i can't find a clear set of alternatives... am i missing a step?
Click to expand...
Click to collapse
You are missing the space between mmcblk3pX and /sdcard.
ok, thats what i thought. when i do it the other way i get the "failed with Error: -1" any ideas on that. also if i send it back to t-mobile under the warranty, they won't send it back as damaged since i had CMW installed o it will they?
thatruth132 said:
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Click to expand...
Click to collapse
great how to
white99 said:
ok, thats what i thought. when i do it the other way i get the "failed with Error: -1" any ideas on that. also if i send it back to t-mobile under the warranty, they won't send it back as damaged since i had CMW installed o it will they?
Click to expand...
Click to collapse
humz mine wont flash at all
Guys,
If someone can help people struck here like me, it would be great.. i get the same -1 error message... when i run the second command. the first one passes through and i get a # for flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img.
When we downloaded the file boot.img, how would boot_orig.img work? am i missing something?
The second command throws me an error..
Guys really waiting for help... bricked my streak in hours after i brought it..
where are you at in la
I need a little bit of help for an ex-ipohone user
Hey guys sorry to ask u a noob question, but can anyone give me an ideea how to remove/unistall CWM Recovery so i can send back my Streak 7 for repair? I have installed CWM thru fastboot an i am currently on stock 2.2.2 rom. Or if there is a thread that i didnt find please a little help would be much apreciated.
i have figured it out eventualy after 20 hrs of brain scratching ived used NVflash and worked fast and easy
thatruth132 said:
this guide is for those who still have Clockwork Mod Recovery still on device you can thank bogdi1988 for his work and orginal guide here :
http://forum.xda-developers.com/showpost.php?p=12185475&postcount=76
BUT THIS MAY WORK FOR OTHERS IF YOU KNOW HOW TO MOUNT SYSTEM AND DATA AND THOSE THINGS FROM ADB
but to simplify I did this :
stock images
recovery.img
http://dl.dropbox.com/u/2252176/recovery.img
boot.img
http://dl.dropbox.com/u/2252176/boot.img
Once in recovery mount everything you can system , data , cache , everyrthing besides sd card
then go into command prompt and type adb shell make sure its working if you still have root it will show # if not it will show $ I believe no biggie as long as it picks up in shell.
then type : flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
then type : flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again.
bogdi1988 suggest flash all images over again in fastboot
in this order
system.img
recovery.img
boot.img
thanks go to everyone who has a dell streak 7 that was willing to try all these hacks and risking your devices for the greater good of the streak
P.S. I will post system.img in a second
Also for fastboot help thank bogdi1988 again heres his post that helped me
http://forum.xda-developers.com/showpost.php?p=11929063&postcount=23
Click to expand...
Click to collapse
OMFG I would so kiss you right now. I was stuck where I could only load up CWR and nothing else was working. You are my hero. *sigh*
No biggie just hit that thanks.button
Sent from my Dell Streak 7 using XDA Premium App
The links are down, any mirrors?
Same need files links re not working
IMG Reposted?
Hi Folks,
A couple of people have posted that the boot, recovery, and system image links respond with a "404 not found" error. This is still the case.
I recall reading somewhere else that the images may still live on the SD card on the device. If this is true does someone know where in the file structure they may be?
If not, does anyone know where to obtain the images?
Currently I'm in CWM reboot hades on my Dell Streak 7. Tried the Dell OTA update for Honeycomb...didn't know that was a BAD thing until it was too late.
I've tried flashing boot and recovery images from a backup I'd made earlier, but no luck, so thatruth's excellent guide here: http://forum.xda-developers.com/show....php?t=1006829 doesn't help much...unless I can get the recovery and boot images.
So to reiterate:
I can get to CWM and clear the caches and flash a recovery.
I can communicate with the device via ADB and have flashed it with the backup images.
I can mount the internal SD card via CWM and my pc.
After flashing with the backup images, Fastboot still does not recognize that the device is connected, and the device does not apper to go through the 'format steps'.
Cheers,
L2
Found 'lightly modified' roms (thank you DJ Steve!) for a T-Mobile streak on another XDA thread. Flashed using adb, and tadaaaa, it booted! sliiiight problem. Will not boot into recovery and no wireless.
Managed to install rom manager (AKA ClockWorkMod) via ADB but CWM wan't an internet connection to install the recovery rom. grrrrr.
One of the other modifications (aside from root) by DJ Steve is the installation of 'BusyBox', This actually seems to complicate things for me because I don't really know how to issue ADB commands from the BusyBox shell. I get a lot of 'invalid command' and the like... I was able to install CWM OUTSIDE the adb shell (adb install rommanager) but once I'm in the shell (adb shell)I don't know how to issue the proper commands.
What I want to do is either remove busybox, or use ADB inside busybox to flash the CWM recovery rom, then flash my backup roms. (and hopefully return to full functionality.)
Any suggestions on how to use ADB commands inside of busy box to flash a rom?
Can anyone upload the stock rom images? I need to flash back to stock :\
just a quick tool i put together that unlocks bootloader, flashes a recovery image, installs root, s-off and writes superCID!
simply install the exe file and run it off your desktop(sorry windows only)
FULL FEATURES:
Free Me (Unlock Bootloader, Flashes Recovery, Roots Device, S-OFF, Writes SuperCID)
Show oem token code
Flash oem token
Flash recoveries
Flash recovery themes
My GraffStyleZ TWRP Theme Included
S-Off
Enable root permissions
Force Update
Flash any .zip file
Flash a rom
Create a logcat
Show CID
Write superCID
Backup device
Restore device
Relock bootloader
Flash custom radio
Fix sdcard errors
Fix low batter error
Reboot options
Advanced wipe Options
Pulls Files From Server
Wipe Data
Wipe Cache
Wipe System
Wipe Dalvik Cache
Wipe Android Secure
Wipe Recovery
Wipe Boot img
Wipe Data,Cache
Wipe Data,Cache,System,Dalvik
Automatically Kills adb Upon Completion Of Task
Unlock bootloader guide
Install custom recovery guide
Install recovery theme guide
Enable root permissions guide
Install roms or .zip files guide
Restore device to defaults guide
Click to expand...
Click to collapse
Download Here
REMEMBER! IF YOU LIKE MY TOOL HIT THE THANKS BUTTON OR EVEN BUY ME A KANGAROO!
Ehm..... Just wanted to add a reminder, only use fastboot when it is the only way out. Fastboot can be dangerous, but nice made.
Also here is my testresults:
i did use the function : INSTALL A DOWNLOADED ROM
but:
fastboot erase data -- should be userdata
fastboot erase dalvik -- does not exsist, dalvik-cache is either /cache/dalvik-cache or if i remeber correctly some cm roms uses /data partition to handle dalvik-cache.
and last:
fastboot flash zip --- does not allow you to flash a rom, it complains about it is not allowed to do it, and as i remeber it is our bootloader that are locked on that part.
i tried also with a kernel.zip
sendng "zip" (4029 KB)...
OKAY [ 2.571s]
writing "zip"...
FAILED (remote: not allowed) <----i am s-off and rooted and so on
Finished....
so try do it like a openrecovery scripts using recovery
and last:
the fix low battery error, can you explain how that works
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
ehm
anders3408 said:
Ehm..... Just wanted to add a reminder, only use fastboot when it is the only way out. Fastboot can be dangerous, but nice made.
Also here is my testresults:
i did use the function : INSTALL A DOWNLOADED ROM
but:
fastboot erase data -- should be userdata
fastboot erase dalvik -- does not exsist, dalvik-cache is either /cache/dalvik-cache or if i remeber correctly some cm roms uses /data partition to handle dalvik-cache.
and last:
fastboot flash zip --- does not allow you to flash a rom, it complains about it is not allowed to do it, and as i remeber it is our bootloader that are locked on that part.
i tried also with a kernel.zip
sendng "zip" (4029 KB)...
OKAY [ 2.571s]
writing "zip"...
FAILED (remote: not allowed) <----i am s-off and rooted and so on
Finished....
so try do it like a openrecovery scripts using recovery
and last:
the fix low battery error, can you explain how that works
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
ehm
Click to expand...
Click to collapse
i have flashed .zip files on other phones like nexus and desire hd, it was successful, but i have not tried it on sxl as do not have the device anymore but seeing as developers gave so much to me from this forum, i thought id give a little back before i move on to learning ios development, try manual adb and executing adb root then flashing your kernel or zip
i havent tested roms yet though
as of the flashing kernel.zip, i do not know why it did not flash, maybe also try the adb root command before flashing?
and on some devices your phone will not charge it bootloader or recovery and when you want to revert back to stock os, no root, no custom recovery etc. some peoples devices fail to restore after the phone wipes system, data and cache partitions while there battery is below i think 18 percent, and fastboot wont allow you to boot into recovery until battery is above that amount.
why dont they turn their phone off abd let it charge? because when they connect the charger the phone boot into bootloader
i found a guide on google the other week as a request of adding the feature and those commands worked
this is a beta, thanks for the bug reports, will update it and fix the bugs later tonight
our bootloader does not support flashing zip files, that part is locked even if s-off
anders3408 said:
our bootloader does not support flashing zip files, that part is locked even if s-off
Click to expand...
Click to collapse
well thanks for your advice great help, need more people who give great accurate feedback like you will fix most of these errors in the update!
ricky310711 said:
well thanks for your advice great help, need more people who give great accurate feedback like you will fix most of these errors in the update!
Click to expand...
Click to collapse
You can try something like this example:
make a OpenRecoveryScript called flash_rom
adb shell mkdir /cache/recovery/openrecoveryscript
adb push flash_rom /cache/recovery/openrecoveryscript
adb reboot bootloader
fastboot boot twrp-recovery.img
i dont know how to get it to start the script, perhaps it is enough to push the script to correct folder and then boot recovery up.
The reason for fastboot boot ..... is for all can use it also if they uses cwm or a outdated recovery
More info :
http://www.teamw.in/OpenRecoveryScript
https://github.com/JBirdVegas/andro...installer/OpenRecoveryScriptSupport.java#L265
and here is what i also found, that is being done via an app called tasker from android, but i guess it should give us an idear on how it works
1) Use the Secure Settings plugin to run the command as root:
date=`date +%Y.%m.%d-%H.%M`;echo -e "wipe cache\nwipe dalvik\nbackup SDBO $date" > /cache/recovery/openrecoveryscript
2) then choose task > wait and set it for 5 seconds (giving time for things to settle
3) Use Secure Settings plugin as root again to run the command:
echo 'boot-recovery' > /dev/block/mmcblk0p3; sync; reboot <--------mmcblk..... should ofc be changed so it fits runnymede.
i think that is the only way you can flash a rom automaticly on runnymede, but what you can do is, push the rom to zip and when done reboot to recovery and i guess people knows how to press a few buttons
anders3408 said:
You can try something like this example:
make a OpenRecoveryScript called flash_rom
adb shell mkdir /cache/recovery/openrecoveryscript
adb push flash_rom /cache/recovery/openrecoveryscript
adb reboot bootloader
fastboot boot twrp-recovery.img
i dont know how to get it to start the script, perhaps it is enough to push the script to correct folder and then boot recovery up.
The reason for fastboot boot ..... is for all can use it also if they uses cwm or a outdated recovery
More info :
http://www.teamw.in/OpenRecoveryScript
https://github.com/JBirdVegas/andro...installer/OpenRecoveryScriptSupport.java#L265
and here is what i also found, that is being done via an app called tasker from android, but i guess it should give us an idear on how it works
1) Use the Secure Settings plugin to run the command as root:
date=`date +%Y.%m.%d-%H.%M`;echo -e "wipe cache\nwipe dalvik\nbackup SDBO $date" > /cache/recovery/openrecoveryscript
2) then choose task > wait and set it for 5 seconds (giving time for things to settle
3) Use Secure Settings plugin as root again to run the command:
echo 'boot-recovery' > /dev/block/mmcblk0p3; sync; reboot <--------mmcblk..... should ofc be changed so it fits runnymede.
i think that is the only way you can flash a rom automaticly on runnymede, but what you can do is, push the rom to zip and when done reboot to recovery and i guess people knows how to press a few buttons
Click to expand...
Click to collapse
i will look into that, as im sure you know i have only just started development, im still learning from people like, but am gonna give back as much as i have took
So this tool basicly roots the sxl for ya am I right going to give it a try today if it does
Sent from my GT-N7105 using xda premium
First,
*
Grateful for the help and attention of those who saw it then
*
My problem is the following,
I own a Razr - XT890 JB. (To my knowledge, the last update provided by Software him, was the "Claro Brazil")
*
I modified my build.prop Mobile, everything went well,
More on grounds of extreme stupidity mine, I opted to return the original
however, when you replace the file did not give priority to the recording file, as it should have done, and rebooted the machine, all unintentionally;
*
From there, caught in the Bootloader screen
*
I tried different ROMs, which came closest is the XDA Rom,RazRi_JB_X-2014-Jul-11.zip
She reaches in the Rom Boot screen, install everything perfectly, plus al relates to a Bootloader,
Other Roms give error, or error in / system / build.prop other give that error related command line "getvar max-download-size"
*
Please, I request immediate help, RSD does not also recognize the device to which the installation commands from it, and I have no great knowledge to try to "solo" via SDK commands, correct me about the errors.
*
But here I am, if you have a forum that I still have hope that helps me is this,
*
If anyone can (and if they work of course) upload or give me a link of a BKP-ROM of this apparatus, I believe that giving the System Restore Partition with Original Build.prop everything is working again, I searched for a good gringos forums , and saw some similar cases are resolved well, but with other devices.
*
*
I hope I was clear enough.
*
*
Without more,
Thank you again.
From A very desperate Brazilian
klizardstz said:
First,
*
Grateful for the help and attention of those who saw it then
*
My problem is the following,
I own a Razr - XT890 JB. (To my knowledge, the last update provided by Software him, was the "Claro Brazil")
*
I modified my build.prop Mobile, everything went well,
More on grounds of extreme stupidity mine, I opted to return the original
however, when you replace the file did not give priority to the recording file, as it should have done, and rebooted the machine, all unintentionally;
*
From there, caught in the Bootloader screen
*
I tried different ROMs, which came closest is the XDA Rom,RazRi_JB_X-2014-Jul-11.zip
She reaches in the Rom Boot screen, install everything perfectly, plus al relates to a Bootloader,
Other Roms give error, or error in / system / build.prop other give that error related command line "getvar max-download-size"
*
Please, I request immediate help, RSD does not also recognize the device to which the installation commands from it, and I have no great knowledge to try to "solo" via SDK commands, correct me about the errors.
*
But here I am, if you have a forum that I still have hope that helps me is this,
*
If anyone can (and if they work of course) upload or give me a link of a BKP-ROM of this apparatus, I believe that giving the System Restore Partition with Original Build.prop everything is working again, I searched for a good gringos forums , and saw some similar cases are resolved well, but with other devices.
*
*
I hope I was clear enough.
*
*
Without more,
Thank you again.
From A very desperate Brazilian
Click to expand...
Click to collapse
As i can read from your post, u do have an unlocked bootloader and u do have installed a custom recovery. U can access the recovery and wipe partitions. If so, all can be solved.
A build.prop change may get you a bootloop, but shouldn't be able to remove the device installation methods and booting of other roms.
There is a huge chance that something in your data partition doesn't match the things that the rom wants to boot, so u get the bootloop. What it is can be difficult to say, only a logcat can provide answers if it works.
There are 4 methods to solve this.
1. hope logcats works and find the root of the problem (can be very difficult, if u dont know what logcat does and how it works)
2. download a custom rom, wipe the system, data and cache partitions and install a fresh custom rom
3. download your newest firmware from here and install by RSD lite when in Fastboot mode (power + volume down)
4. manually flash and wipe the new firmware
D:
Hazou said:
As i can read from your post, u do have an unlocked bootloader and u do have installed a custom recovery. U can access the recovery and wipe partitions. If so, all can be solved.
A build.prop change may get you a bootloop, but shouldn't be able to remove the device installation methods and booting of other roms.
There is a huge chance that something in your data partition doesn't match the things that the rom wants to boot, so u get the bootloop. What it is can be difficult to say, only a logcat can provide answers if it works.
There are 4 methods to solve this.
1. hope logcats works and find the root of the problem (can be very difficult, if u dont know what logcat does and how it works)
2. download a custom rom, wipe the system, data and cache partitions and install a fresh custom rom
3. download your newest firmware from ## and install by RSD lite when in Fastboot mode (power + volume down)
4. manually flash and wipe the new firmware
Click to expand...
Click to collapse
Sorry for the delay dear friend.
I am currently without a computer and unable to respond, since the cell has not returned to work,
tried the "LogCat" and without success, a message that has no logs, not even the XDA App worked,
Should I start worrying?
Also already tried several ROM'S, the only one that installs with success is that I found here on XDA, however the bootloop, since other, or withdrawing the "GetJar" they conclude.
Someone to help this desperate soul?
Grateful friends.
You are my last hope.
klizardstz said:
Sorry for the delay dear friend.
I am currently without a computer and unable to respond, since the cell has not returned to work,
tried the "LogCat" and without success, a message that has no logs, not even the XDA App worked,
Should I start worrying?
Also already tried several ROM'S, the only one that installs with success is that I found here on XDA, however the bootloop, since other, or withdrawing the "GetJar" they conclude.
Someone to help this desperate soul?
Grateful friends.
You are my last hope.
Click to expand...
Click to collapse
I don't get you very good. Just answer my questions so i understand your situation better.
1. How are u installing those roms?
2. Do u have a custom recovery?
3. If u have a custom recovery do u have a nandroid backup to restore your data?
4. If u are installing a new rom from here on xda, do u format system, data, cache? (full wipe)
5. If u still don't know. Read "INDEX/GUIDE, ALL Things RAZR I". Link under this. And go to "J". Read the instructions and read how to use RSD-Lite and were to download your latest firmware.
I have the feeling u are new to android. (maybe i am wrong, sorry) Just an advise for further things, always have a backup plan.
Hope this helps, i will hear it.
Hazou said:
I don't get you very good. Just answer my questions so i understand your situation better.
1. How are u installing those roms?
2. Do u have a custom recovery?
3. If u have a custom recovery do u have a nandroid backup to restore your data?
4. If u are installing a new rom from here on xda, do u format system, data, cache? (full wipe)
5. If u still don't know. Read "INDEX/GUIDE, ALL Things RAZR I". Link under this. And go to "J". Read the instructions and read how to use RSD-Lite and were to download your latest firmware.
I have the feeling u are new to android. (maybe i am wrong, sorry) Just an advise for further things, always have a backup plan.
Hope this helps, i will hear it.
Click to expand...
Click to collapse
Answers:
1 - Various shapes, tried by RSD 6.1.5 and also tried the 6.1.4, I have tried sideloading, and the Recovery of the XT890, both insalam not only the rom I mentioned above
2 - If by "Custom Recovery" you referred to CWM own the "CWM-based Recovery v6.0.1.5" version (Otherwise understand the fast stuff, just redirect me what you mean.)
3 - I do not have backups, just a backup I made before starting the procedures, then my build.prop is still without overwriting permissions
4 - Yes, always before any attempts, I place one Wipe data / factory reset, and still enter the sector of partitions and format the partitions, I'll mount / system, / cache, / data, / and the inside of virtual which is represented as a SDCARD format, all of them, and then install the ROM.
5 - As for reading, I'll check, As the experience in Android, I am not so layman, plus the more technical parts'm starting to learn now, as self-taught, I have extensive knowledge in the areas of computer science and a good reasoning, I believe it will be easy to be guided by you;
Thanks again for the attention paid to me. :good:
klizardstz said:
Answers:
1 - Various shapes, tried by RSD 6.1.5 and also tried the 6.1.4, I have tried sideloading, and the Recovery of the XT890, both insalam not only the rom I mentioned above
2 - If by "Custom Recovery" you referred to CWM own the "CWM-based Recovery v6.0.1.5" version (Otherwise understand the fast stuff, just redirect me what you mean.)
3 - I do not have backups, just a backup I made before starting the procedures, then my build.prop is still without overwriting permissions
4 - Yes, always before any attempts, I place one Wipe data / factory reset, and still enter the sector of partitions and format the partitions, I'll mount / system, / cache, / data, / and the inside of virtual which is represented as a SDCARD format, all of them, and then install the ROM.
5 - As for reading, I'll check, As the experience in Android, I am not so layman, plus the more technical parts'm starting to learn now, as self-taught, I have extensive knowledge in the areas of computer science and a good reasoning, I believe it will be easy to be guided by you;
Thanks again for the attention paid to me. :good:
Click to expand...
Click to collapse
okey, so u have some experience. I just misunderstood you then. my bad, sorry.
Even with a full wipe/format of everything and installing a custom rom u can't get it to boot. It will stay in a bootloop or even worse, don't go past the bootloader unlock screen.
With RSD-Lite (administrator) 6.1.6, 6.1.5 and 6.1.4 and all the drivers installed correctly and ready to run it won't recognize your phone when it is in (ap) fastboot mode. And if it recognizes your phone. At what part does it give an error, what is the error in rsd-lite/phone screen? Getvar error is more like a warning. We can disable that one.
Never seen this what u have. Because u can get into recovery, but the device won't boot. Will wait at your next post to confirm the above
Hazou said:
okey, so u have some experience. I just misunderstood you then. my bad, sorry.
Even with a full wipe/format of everything and installing a custom rom u can't get it to boot. It will stay in a bootloop or even worse, don't go past the bootloader unlock screen.
With RSD-Lite (administrator) 6.1.6, 6.1.5 and 6.1.4 and all the drivers installed correctly and ready to run it won't recognize your phone when it is in (ap) fastboot mode. And if it recognizes your phone. At what part does it give an error, what is the error in rsd-lite/phone screen? Getvar error is more like a warning. We can disable that one.
Never seen this what u have. Because u can get into recovery, but the device won't boot. Will wait at your next post to confirm the above
Click to expand...
Click to collapse
Yes, I have some experience, nothing more than apologize, who should apologize me for the inconvenience,
anyway ...
6.1.6 not tried, however, all other dao errors, and they are variable, depending on the rum,
Ex: Error 1/11, 6/12/8/10 and etc ...
already in CWM also varies, but with other command lines, and yes, even with all procedures, with pull and push the build.prop files, giving the command "chmod 644 build.prop" or even chmod 777 apparently can not the permiçoes there a way to delete the build, and relocate it on the partition / system?
also could not find any error like this, evil technology is that it seems that every problem is like a biological virus, mutates and hinders every time. LOL, since I do not know what to do: /
I look carefully your help friend.
* I've tried replacing build.prop, the original, by others, by the Galaxy S2, nothing more useless
as the part that mentioned at the end of your post, yes, I can do everything, however nothing stops the bootloop.
any suggestions?
klizardstz said:
Yes, I have some experience, nothing more than apologize, who should apologize me for the inconvenience,
anyway ...
6.1.6 not tried, however, all other dao errors, and they are variable, depending on the rum,
Ex: Error 1/11, 6/12/8/10 and etc ...
already in CWM also varies, but with other command lines, and yes, even with all procedures, with pull and push the build.prop files, giving the command "chmod 644 build.prop" or even chmod 777 apparently can not the permiçoes there a way to delete the build, and relocate it on the partition / system?
also could not find any error like this, evil technology is that it seems that every problem is like a biological virus, mutates and hinders every time. LOL, since I do not know what to do: /
I look carefully your help friend.
* I've tried replacing build.prop, the original, by others, by the Galaxy S2, nothing more useless
as the part that mentioned at the end of your post, yes, I can do everything, however nothing stops the bootloop.
any suggestions?
Click to expand...
Click to collapse
I have 2 more suggestions.
1. we manually flash/erase all things through mfastboot and see what happens.
2. We need a micro sdcard and we move the system partition from your phones internal memory to your sdcard, so it can boot from your sdcard. Because you have access to recovery and boot we can try this.
But i need some more time to write this up. especially the second thing. Never done it, but it is possible seen it before and read it. u can search around on the internet about those 2 things before we try anything. Will follow your post or edit this one with the worked out suggestions.
What i find weird about all this. U said u formatted all the partitions and even then with the right stock firmware from your mobile it wouldn't boot or anything. And the formatting off the partitions did work, so there should be no error anywhere normally. Because it does mean there is no memory error and the recovery can read and write stuff. U do have the xt890 and the right stock firmware (JB), don't u?
And next to that. After installing a new rom (with formatting of all partitions(system/cache/data)) u still try to change the build.prop. After a format it shouldn't be there anymore. Can u format everything (manually, not with full wipe, but with the options format system etc., again only system, cahce and ata or u can screw it even more ) again and see with adb through recovery if there is any file left on the system partition. Mount /system and do in adb shell in recovery a search for the build.prop. When in adb shell the command "ls system" should give u a list with all the files in it.
Hazou said:
I have 2 more suggestions.
1. we manually flash/erase all things through mfastboot and see what happens.
2. We need a micro sdcard and we move the system partition from your phones internal memory to your sdcard, so it can boot from your sdcard. Because you have access to recovery and boot we can try this.
But i need some more time to write this up. especially the second thing. Never done it, but it is possible seen it before and read it. u can search around on the internet about those 2 things before we try anything. Will follow your post or edit this one with the worked out suggestions.
What i find weird about all this. U said u formatted all the partitions and even then with the right stock firmware from your mobile it wouldn't boot or anything. And the formatting off the partitions did work, so there should be no error anywhere normally. Because it does mean there is no memory error and the recovery can read and write stuff. U do have the xt890 and the right stock firmware (JB), don't u?
And next to that. After installing a new rom (with formatting of all partitions(system/cache/data)) u still try to change the build.prop. After a format it shouldn't be there anymore. Can u format everything (manually, not with full wipe, but with the options format system etc., again only system, cahce and ata or u can screw it even more ) again and see with adb through recovery if there is any file left on the system partition. Mount /system and do in adb shell in recovery a search for the build.prop. When in adb shell the command "ls system" should give u a list with all the files in it.
Click to expand...
Click to collapse
I'll look around this friend, I wonder if I can really expect his return to the subject, you have been the one to support me here, and do not locate anything about the internet.
So your recommendation would be to wait or try to?
Because ruin even more ...
I have the sd card and just download the mfastboot-v2.zip
make a backup of the rom and try what then?
Is there any tutorial link, or can guide me trough this process?
If it is not possible to just show me that not of, and the way I try, the second part I do not know how to do, never read about it, but I will also look ...
Run the risk of damaging the hardware?
klizardstz said:
I'll look around this friend, I wonder if I can really expect his return to the subject, you have been the one to support me here, and do not locate anything about the internet.
So your recommendation would be to wait or try to?
Because ruin even more ...
I have the sd card and just download the mfastboot-v2.zip
make a backup of the rom and try what then?
Is there any tutorial link, or can guide me trough this process?
If it is not possible to just show me that not of, and the way I try, the second part I do not know how to do, never read about it, but I will also look ...
Run the risk of damaging the hardware?
Click to expand...
Click to collapse
Ok, to fast to much
First do this and post the results.
1. reboot in recovery
2. connect phone (in recovery mode) with usb to PC
3. check with adb if the pc can see the phone with the command: "adb devices". Should give u a device. Name should be a sequence of numbers
4. if in step 3 you get a phone. Type "adb remount" and enter
5. type: "adb shell" and enter
6. type: "mount /system" and enter
7. type: "ls /system" and enter
8. post the results of step 7.
We will see after this what to do next
Results
Hazou said:
Ok, to fast to much
First do this and post the results.
1. reboot in recovery
2. connect phone (in recovery mode) with usb to PC
3. check with adb if the pc can see the phone with the command: "adb devices". Should give u a device. Name should be a sequence of numbers
4. if in step 3 you get a phone. Type "adb remount" and enter
5. type: "adb shell" and enter
6. type: "mount /system" and enter
7. type: "ls /system" and enter
8. post the results of step 7.
We will see after this what to do next
Click to expand...
Click to collapse
So come on friends,
So ... to start already gave an error that bothered me before.
Post the picture, damn contradiction failed: Success
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here's the result ....
hmm, that doesn't look bad.
We try the following steps to get you back to stock. Every step needs to give an 'OKEY' if not, report here.
For this we need to have mfastboot. So download it and set it up.
Download your latest official firmware (4.1.2) for your device. So coming from EU use EU, BR use BR etc. And extract it. Copy mfastboot into those files or copy all the files into the mfastboot directory file.
1. reboot in bootloader
2. do: 'mfastboot devices' and you get medfield******** device. If not, your drivers and mfastboot are not setup properly
3. do: 'mfastboot flash gpt gpt_signed' get 'OKEY'
4. do: 'mfastboot flash motoboot motoboot' get 'OKEY'
5. do: 'mfastboot flash boot boot_signed' get 'OKEY'
6. do: 'mfastboot flash recovery recovery_signed' get 'OKEY'
7. do: 'mfastboot flash motobp motobp' get 'OKEY'
8. do: 'mfastboot flash system sysem_signed' get 'OKEY'
9. do: 'mfastboot flash cdrom cdrom_signed' get 'OKEY'
10. do: 'mfastboot erase cache' get 'OKEY'
11. do: 'mfastboot erase userdata' get 'OKEY'
Report back with what u get. I hope that if u get any error we can fix it.
Hazou said:
hmm, that doesn't look bad.
We try the following steps to get you back to stock. Every step needs to give an 'OKEY' if not, report here.
For this we need to have mfastboot. So download it and set it up.
Download your latest official firmware (4.1.2) for your device. So coming from EU use EU, BR use BR etc. And extract it. Copy mfastboot into those files or copy all the files into the mfastboot directory file.
1. reboot in bootloader
2. do: 'mfastboot devices' and you get medfield******** device. If not, your drivers and mfastboot are not setup properly
3. do: 'mfastboot flash gpt gpt_signed' get 'OKEY'
4. do: 'mfastboot flash motoboot motoboot' get 'OKEY'
5. do: 'mfastboot flash boot boot_signed' get 'OKEY'
6. do: 'mfastboot flash recovery recovery_signed' get 'OKEY'
7. do: 'mfastboot flash motobp motobp' get 'OKEY'
8. do: 'mfastboot flash system sysem_signed' get 'OKEY'
9. do: 'mfastboot flash cdrom cdrom_signed' get 'OKEY'
10. do: 'mfastboot erase cache' get 'OKEY'
11. do: 'mfastboot erase userdata' get 'OKEY'
Report back with what u get. I hope that if u get any error we can fix it.
Click to expand...
Click to collapse
Glad for his preliminary Topic...
However, at the first command line can not, aliases, I tried the following, by having obtained the medfield by adb devices, however the following are recognized as command, however not result in anything ...
I downloaded several fastboot. put in the platform-tools, copied the files Adb & Co. as indicated on the internet, however to no avail, any suggestions?
Here's the Dammit CMD Lines.
U need to be in fastboot (bootloader) mode. From recovery u can get there by doing 'adb reboot bootloader' but the fastest way is just reboot your phone with the key combination volume down + power.
Fastboot mode is the mode before u enter recovery. It is also called bootloader.
Verstuurd van mijn GT-P5110
Youre rock!
Hazou said:
U need to be in fastboot (bootloader) mode. From recovery u can get there by doing 'adb reboot bootloader' but the fastest way is just reboot your phone with the key combination volume down + power.
Fastboot mode is the mode before u enter recovery. It is also called bootloader.
Verstuurd van mijn GT-P5110
Click to expand...
Click to collapse
My dear friend,
I have only two more questions for you,
1-How to turn you into a God?
HUEHUEHUE
2-How to increase your reputation?
- At first, the phone would not update the motoboot, however I had the idea to go giving procedure at all, and by the penultimate system, since it would give flash remake the build.prop. and then the motoboot was smoothly. like a feather on a cliff.
Really do not have words enough to thank you all this support that during all this time gave me.
Consider the topic as closed, and for others who have the same problem, I recommend reading it.
You are a Genius emerged from a magic lamp friend.
eternally Grateful
:good::victory:
1. Could be a problem, maybe if u have connections to Zeus, god, Allah or whoever XD
2. U can hit the thanks button under my posts if u want
Glad to hear all is fine now good luck with whatever u want to do now!
Verstuurd van mijn GT-P5110