Related
My prime is stuck in the splash screen and I can't get it to go further than that. I've been reading and been told I can push the ROMs zip file with the adb push command. The zip I downloaded on my computer is in my downloads folder. What would I exactly need to put in the command window to push the zip to the internal memory of my prime?
Sent from my Galaxy Nexus using xda premium
Nilsonf said:
My prime is stuck in the splash screen and I can't get it to go further than that. I've been reading and been told I can push the ROMs zip file with the adb push command. The zip I downloaded on my computer is in my downloads folder. What would I exactly need to put in the command window to push the zip to the internal memory of my prime?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Number 1, stick your ROM into the same folder that adb is in.
Number 2, read up about command line and terminal. (Trust me, you should do this)
Number 3, with your new found knowledge, push that file onto your internal storage. Example "adb push /ROM.zip /sdcard" !!!!!!
It's as simple as that sometimes.
The thing I don't get is what am I supposed to put on the adb push /ROM.zip /sdcard part
Sent from my Galaxy Nexus using xda premium
adb
Run adb devices, this will let you know if your drivers are working correctly, you should get
Recovery and your devices serial number, then if your zip is named virtuous.zip the command line is,
adb push virtuous.zip /sdcard/
You put the name of the zip file in there to push, /sdcard/ puts it on your root directory.
dklue said:
Run adb devices, this will let you know if your drivers are working correctly, you should get
Recovery and your devices serial number, then if your from zip is named virtuous.zip the command line is,
ad push virtuous.zip /sdcard/
You put the name of the zip file in there to push, /sdcard/ puts it on your root directory.
Click to expand...
Click to collapse
I've been doing that but it doesn't work
Sent from my Galaxy Nexus using xda premium
adb
Can you put it into cwm recovery ? When off hold volume down and the power button,
When little white letters come up, hit volume up, it should be in cwm when your adb pushing files, you can also try continuing to hold down on volume and then you get the three choices,
Android, USB, wipe data, it may push in the USB choice, read in the development section how
to unbrick your transformer prime, hopefully its a soft brick.
dklue said:
Can you put it into cwm recovery ? When off hold volume down and the power button,
When little white letters come up, hit volume up, it should be in cwm when your adb pushing files, you can also try continuing to hold down on volume and then you get the three choices,
Android, USB, wipe data, it may push in the USB choice, read in the development section how
to unbrick your transformer prime, hopefully its a soft brick.
Click to expand...
Click to collapse
Yeah when I try to push the file its in CWM and I type adb devices it recognizes it in recovery and the serial. I put adb push Primalicious_9.4.2.21._Final.zip /sdcard/ enter and it says no such file. Is it supposed to be in a specific folder or am I doing something wrong? I already unbricked it I just need to load the ROM
Sent from my Galaxy Nexus using xda premium
adb
The rom zip file should be in the directory where your adb.exe is. So if its in say
Program files/android/tools that's where you need to put the zip, otherwise it won't know
Where it is.
dklue said:
The rom zip file should be in the directory where your adb.exe is. So if its in say
Program files/android/tools that's where you need to put the zip, otherwise it won't know
Where it is.
Click to expand...
Click to collapse
Is this right?
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
adb
Yes that's right, you may want to rename it prime.zip, cause it may be .zip.zip or something,
or it may be a zip inside a zip.
dklue said:
Yes that's right, you may want to rename it prime.zip, cause it may be .zip.zip or something,
or it may be a zip inside a zip.
Click to expand...
Click to collapse
So rename the ROM prime.zip? And try that?
Sent from my Galaxy Nexus using xda premium
adb
You need to put the full file name,
adb push primalicious.zip /sdcard/
That's just the example, put the correct name in and include .zip.
I changed the name to prime.zip so I tried adb push prime.zip /sdcard/ and adb push prime.zip.zip /sdcard/ and it says no files found
Sent from my Galaxy Nexus using xda premium
adb
Do you have a backup to restore in cwm ? Or try to unmount /staging and mount /Data
In cwm and try
adb push prime.zip /data/local/
Otherwise I'm not sure why its not recognizing that file, I bricked my prime and someone in irc channel sent me a blob file, and he told me to push it to /data/local/
And it worked, I had to use win xp cause I couldn't get it to work on win 7, but your getting the correct response from adb devices, so I'm not sure,
---------- Post added at 09:22 PM ---------- Previous post was at 09:11 PM ----------
http://android.dkszone.net/copy-transfer-files-android-sd-card-adb-windows
dklue said:
Do you have a backup to restore in cwm ? Or try to unmount /staging and mount /Data
In cwm and try
adb push prime.zip /data/local/
Otherwise I'm not sure why its not recognizing that file, I bricked my prime and someone in irc channel sent me a blob file, and he told me to push it to /data/local/
And it worked, I had to use win xp cause I couldn't get it to work on win 7, but your getting the correct response from adb devices, so I'm not sure,
Click to expand...
Click to collapse
Ok thank you for your help. I will try to do that tomorrow cause I'm tired of messing with it for tonight lol. Hopefully I can get it to work
Sent from my Galaxy Nexus using xda premium
FIX!! - How to adb a zip ROM through CWM!!!
Hello there, for the last few nights I was having the same issue as you. I bricked my tablet, fixed it, and then just got stocked on the recovery with no data on my SDCARD. After searching and searching for hours online I found your post last night. And after reading the comments from "dklue", i googled some more information about something very important that me and you were missing!: "Blob files".
The "Primalicious_9.4.2.21._Final.zip" file or the "AOKP.zip" file will not work just like that because they are not in the format to be "Pushed" using the push command (At least thats what i kinda realized lol) anyhow, so i went online and searched for a ROM on Blob format and luckily i found the following!:
[ROM][WW][US][9.4.2.21] Primeval: The STOCK stock rom
So here is what worked for me thanks God! lol (Keep in mind that for some reason this process did not work for me on the new "CWM Touch Recovery 5.8.1.8" I actually had to downgrade my CWM to the 5.5.0.4 Version, you can download it from here:
androidroot . mobi / 2012 / 02/22/introducing-cwm-for-asus-transformer-prime/ --> WITH NO SPACE in between!
Here is how to Install the CWM file on your prime:
1. Get fastboot from that website, and extract it.
2. Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
3. Power off your prime.
4. Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot” -> USB ICON.
5. Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
6. Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
7. Reboot
-----------------------------------------------------------------------------------------
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "dklue" gave me the BLOB concept idea! heheheh i guess i learned something new now..
djedoortega said:
Hello there, for the last few nights I was having the same issue as you. I bricked my tablet, fixed it, and then just got stocked on the recovery with no data on my SDCARD. After searching and searching for hours online I found your post last night. And after reading the comments from Nilsonf, i googled some more information about something very important that me and you were missing!: "Blob files".
The "Primalicious_9.4.2.21._Final.zip" file or the "AOKP.zip" file will not work just like that because they are not in the format to be "Pushed" using the push command (At least thats what i kinda realized lol) anyhow, so i went online and searched for a ROM on Blob format and luckily i found the following!:
[ROM][WW][US][9.4.2.21] Primeval: The STOCK stock rom
So here is what worked for me thanks God! lol (Keep in mind that for some reason this process did not work for me on the new "CWM Touch Recovery 5.8.1.8" I actually had to downgrade my CWM to the 5.5.0.4 Version, you can download it from here:
androidroot . mobi / 2012 / 02/22/introducing-cwm-for-asus-transformer-prime/ --> WITH NO SPACE in between!
Here is how to Install the CWM file on your prime:
1. Get fastboot from that website, and extract it.
2. Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
3. Power off your prime.
4. Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot” -> USB ICON.
5. Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
6. Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
7. Reboot
-----------------------------------------------------------------------------------------
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "Nilsonf" gave me the BLOB concept idea! heheheh i guess i learned something new now..
Click to expand...
Click to collapse
Thanks man. I'll have to try that sometime later on today. I will report back with the end results
Sent from my Galaxy Nexus using xda premium
I'm stuck on number 3 of part 2. It's been doing nothing for about 20 minutes now. Should I keep waiting?
I downloaded it from here ww w.clockworkmod.co m/rommanager/
I got the 5.8.4.3 image for my att note
(sorry I need to post more)
I have put it on my internal sd card and renamed it to recovery then I used my terminal emulator to use the command
su
flash_image recovery /sdcard/recovery.img
then it says it cant find it.
What am I missing?
rogsoccerman said:
I downloaded it from here ww w.clockworkmod.co m/rommanager/
I got the 5.8.4.3 image for my att note
(sorry I need to post more)
I have put it on my internal sd card and renamed it to recovery then I used my terminal emulator to use the command
su
flash_image recovery /sdcard/recovery.img
then it says it cant find it.
What am I missing?
Click to expand...
Click to collapse
Use odin.... thats what i done worked perfect!
Sent from my SAMSUNG-SGH-I717 using xda premium
How do I Odin a recovery image? I thought you need a tar file.
rogsoccerman said:
How do I Odin a recovery image? I thought you need a tar file.
Click to expand...
Click to collapse
Scroll on down this thread and u will find the tar file for odin and it will fix ur problems
Sent from my SAMSUNG-SGH-I717 using xda premium
rogsoccerman said:
How do I Odin a recovery image? I thought you need a tar file.
Click to expand...
Click to collapse
Its a little bit farther down someone already made the same thread ur file is there hope it helps let me know
Sent from my SAMSUNG-SGH-I717 using xda premium
Link please I can't find what you are talking about, all I can find is the old version by braway.
Thank you
rogsoccerman said:
I downloaded it from here ww w.clockworkmod.co m/rommanager/
I got the 5.8.4.3 image for my att note
(sorry I need to post more)
I have put it on my internal sd card and renamed it to recovery then I used my terminal emulator to use the command
su
flash_image recovery /sdcard/recovery.img
then it says it cant find it.
What am I missing?
Click to expand...
Click to collapse
I get the same problem as root in terminal:
flash_image recovery /mnt/sdcard/recovery.img
error scanning partitions: no such file or directory
- ROM Manager won't work; the "flash touch recovery" says "not supported" on this phone. The recovery download also doesn't work; the Galaxy Note is not listed, despite it being on the clockworkmod website!
- ODIN won't work as it needs a tar file or md5, or similar.
- There is no tar file in this thread or anywhere else I can find. If anyone knows exactly where this can be found, that would be helpful!
Basically, if I could find an easy way to "tar" up the recovery.img, it might work with ODIN. This might work, as past tars had only the one file within, but I need a UNIX OS to use the tar command. Drat!
UPDATE: I tarred it in the terminal and will now try ODIN. I hope it works....
UPDATE #2 - yep, it works!
How to install
Odin (this will increase the flash counter)
- put your phone into download mode
- in odin choose pda, and select the .tar.md5 file and flash
http://forum.xda-developers.com/showthread.php?t=1584576
[Recovery] ClockworkMod Based Touch Recovery - 04/14/12
works without any issue.....
Here's how I installed/upgraded CWM to 5.8.4.3 this is an A in Q&A
I was on the April version of CWM and was fat and happy, then I thought I'd try ICS, and didn't much care for what I was finding, then I read about another one I thought I'd try, but it (apparently) required a newer version of CWM, 5.8.4.3 i think.
So ROM Manager from the play store wouldn't do the upgrade for me, kept giving errors.
I'd used odin to install the april .tar, but this new version comes in an .img file.
I downloaded the .img file and placed it on my phone in sdcard (/mnt/sdcard)
searched high and low for a few hours, found a semi-cogent post about how to install it using adb from your PC, i guess.
adb is in the SDK which you can get from here:
http://developer.android.com/sdk/index.html
I installed this and I located adb here: C:\androidsdk\android-sdk-windows\platform-tools
on my PC from the command line (start, run, cmd, ENTER) I changed directories to that directory.
I executed, still on the command line: adb shell
:
This presented me the the octothorpe (hashtag if you must) prompt:#
at the # prompt I entered WITHOUT the double quote, ditto marks (")
"dd if=/sdcard/recovery-clockwork-touch-5.8.4.3-quincyatt.img of=/dev/block/mmcblk0p22"
so it looked like this:
#dd if=/sdcard/recovery-clockwork-touch-5.8.4.3-quincyatt.img of=/dev/block/mmcblk0p22
I pressed enter and it ran pretty quickly and returned to the (apparent) adb prompt # then I typed exit and it dumped me to the C: prompt and I exited that too (so there!), Then I rebooted the phone into recovery mode using one of many nifty reboot apps in the play store, so I don't have to have my fingers holding this slick and slippery buttons.
I verified I was in the new version of CWM, and rebooted to make sure my phone was still breathing... it was so I bailed back into recovery and am now running a backup... then I'll try to install the new ICS ROM, although it looks way too small to me.
I've gathered that the # prompt is the root prompt in adb, so either I'm very lucky and it does this by default, or adb detected my rooted phone... if you've read this far your guess is as good as mine.
I hope this helped someone from having to google for hours and hours into the night, and then not oversleep, not be late to work, not get fired, not go on unemployment, etc.
or not.
if you are running an unsecured kernel, adb should start with root rights of I'm not mistaken...also when you were done moving the recovery file instead of exiting the adb session and the c prompt altogether
You could have simply used the command:
Adb reboot recovery
And in fact..That's all those apps do.
Also of you copy the files in your android sdk platform-tools folder:
Aapt.exe
Adb.exe
Adbwinapi.dll
Adbwinusbapi.dll
Into your main Windows folder, you no longer have to cd to the platform-tools folder, you can use adb as a global command.
bigjoe2675 said:
How to install
Odin (this will increase the flash counter)
- put your phone into download mode
- in odin choose pda, and select the .tar.md5 file and flash
http://forum.xda-developers.com/showthread.php?t=1584576
[Recovery] ClockworkMod Based Touch Recovery - 04/14/12
works without any issue.....
Click to expand...
Click to collapse
That's an older version of cwm touch which is not compatible with some newer rooms.
VoluntaryMan said:
That's an older version of cwm touch which is not compatible with some newer rooms.
Click to expand...
Click to collapse
Really...cus i have been using it since i got the note and have flashed just about every ROM, lol works great for me sir, maybe my phone likes me idk, and yes just about every ROM....k
But hey i could be wrong..., so which ever works...use it, thanks
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I had the same problems... Ended up flashing twrp 2.2.1. But this link will work for you.
http://forum.xda-developers.com/showthread.php?p=28932726
Sent from my SAMSUNG-SGH-I717 using xda premium
CWM Touch [Solved, again]
I got it working very easily...
Heres how.
Got my .img file from http://www.clockworkmod.com/rommanager. Scroll to find Samsung Galaxy Note(ATT)
Changed the name of the file from "recovery.whatever.whatever.quincyatt.img" to "recovery.img"(minus quotes) using es file explorer(root needed)
Moved the file to root of /sdcard = /sdcard/recovery.img
Opened terminal emulator
typed
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
quit
then backed out to home screen and rebooted into my newest CWM Touch recovery.
Hope this helps anyone who needs it
EDIT: Just performed backup and succeeded. saved backup to /sdcard/clockworkmod/backup/
Moving prior braway recovery backups there to see if they are manageable within ROMmanager
This worked for me, thanks!
tyler79durdan said:
I got it working very easily...
Click to expand...
Click to collapse
I know this is old but better late than never...
ClockworkMod Touch Recovery 5.8.4.3 for SGH-I717 .tar file
http://forum.xda-developers.com/showthread.php?p=39037837
your welcome, enjoy
tyler79durdan said:
typed
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
quit
Click to expand...
Click to collapse
I did this, but instead of quit, I wrote "reboot recovery". I'm not sure if that did it, or if it was something else I did wrong, but the phone won't come back up. I checksummed the img I downloaded with another copy of "recovery-clockwork-touch-6.0.4.3-quincyatt.img" that I downloaded, and they matched:
e70ee18c0d63ee18d325c94e2af7a683
Shrug.
Edit: I just flashed it through odin and it worked. To build the tar.md5 I did the following in cygwin:
Code:
mv recovery-clockwork-touch-6.0.4.3-quincyatt.img recovery.img
tar -H gnu -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Okay, another update
Of course I'll provide download links again
DOWNLOAD LINKS:
DropBox
Google Drive
OneDrive
---------------
HOW TO INSTALL:
In case your update installation fails for whatever reason you have to go back to a stock state. We'll first downgrade the watch to an older version (since those are the only IMG files I currently have).
Go to THIS PAGE and download the files (Here's a backup-upload in case they're down - OneDrive Backup)
Boot into bootloader mode (reboot watch > once logo shows up swipe from left upper to right lower corner)
Connect to PC, open CMD in the folder with those files and type "fastboot flash recovery recovery_6.0.1_MEC23G.img", "fastboot flash boot boot_6.0.1_MEC23G.img" and "fastboot flash system system_6.0.1_MEC23G.img"
Reboot to system and either let the watch update itself 2 times (far easier) or...
... boot to recovery and sideload the 2 ZIP-files yourself (you need to update to MWD48B (OneDrive Backup) first, then M1D63H (OneDrive Backup)!)
Anyways, I hope this helped a bit!
Currently trying to pull .img-files for those who still have their LG G Watch so installation will be easier and faster.
EpicLPer said:
Currently trying to pull .img-files for those who still have their LG G Watch so installation will be easier and faster.
Click to expand...
Click to collapse
Install TWRP and from console/adb shell write
Code:
[STRIKE]echo "mmcblk0" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file[/STRIKE]
You'll have access to all patitions on your watch.
ab123321 said:
Install TWRP and from console/adb shell write
Code:
echo "mmcblk0" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file
You'll have access to all patitions on your watch.
Click to expand...
Click to collapse
What will this do exactly? I already managed to pull images with DD, but this also sounds interesting
EpicLPer said:
What will this do exactly? I already managed to pull images with DD, but this also sounds interesting
Click to expand...
Click to collapse
It forces kernel to connect flash-memory (mmcblk0) in your watch to your PC as a disk. So, You'll see partitions as drives.
Then, you'll be able to dd them directly on your PC (if you use Linux, of course)
ab123321 said:
It forces kernel to connect flash-memory (mmcblk0) in your watch to your PC as a disk. So, You'll see partitions as drives.
Then, you'll be able to dd them directly on your PC (if you use Linux, of course)
Click to expand...
Click to collapse
Hm, that sounds quite easier hehe, the TWRP dd way was nice too but I'll try this, thanks!
ab123321 said:
Install TWRP and from console/adb shell write
Code:
echo "mmcblk0" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file
You'll have access to all patitions on your watch.
Click to expand...
Click to collapse
Hm, "sh: write error: No such file or directory"
Oh, because "lun" is the actual file, lun is not a directory.
Edit 2: No, wait what... TWRPs file manager shows me this is a file, not a directory, ADB however tells me this is a directory and not a file??? WTF
EpicLPer said:
Hm, "sh: write error: No such file or directory"
Oh, because "lun" is the actual file, lun is not a directory.
Edit 2: No, wait what... TWRPs file manager shows me this is a file, not a directory, ADB however tells me this is a directory and not a file??? WTF
Click to expand...
Click to collapse
Stolen from Watch R thread fixed:
Code:
cd /sys/devices/virtual/android_usb/android0
echo 0 > enable && echo "adb,mass_storage" > functions && echo "/dev/block/mmcblk0" > f_mass_storage/lun/file && echo 1 > enable
I have about 30 of these phones and people have been asking me how I get SuperSU on them:
https://youtu.be/qkik4q5ERaU
NitroKoS said:
I have about 30 of these phones and people have been asking me how I get SuperSU on them:
https://youtu.be/qkik4q5ERaU
Click to expand...
Click to collapse
In the video, you said Kingroot 4.5
There is new:
Kingroot V5.0.4 should I get it instead?
Handsome Jack said:
In the video, you said Kingroot 4.5
There is new:
Kingroot V5.0.4 should I get it instead?
Click to expand...
Click to collapse
Successfully rooted the Alcatel Streak with KingRoot. But my cell phone won't boot after I applied the KingRoot/SuperSu replacement.
Here is thread on requesting ROM to recover from the issue. Obviously another person had same issue as I did:
https://forum.xda-developers.com/android/help/requesting-alcatel-4060-o-cricket-stock-t3578896
I have uploaded all the partition dd image at mediafire.com excepect /system witch is big file and i have low bandwidth
Note, the recovery image is compressed zip us unzip before dd back
kdm6389 said:
I have uploaded all the partition dd image at mediafire excepect /system witch is big file and i have low bandwidth
Note, the recovery image is compressed zip us unzip before dd back
Click to expand...
Click to collapse
I see many dd files with one particular zip file in mediafire. How can I use these files to flash my Alcatel Streak ROM? I have never done this before and I am newbie here.
Thanks,
jxzz said:
I see many dd files with one particular zip file in mediafire. How can I use these files to flash my Alcatel Streak ROM? I have never done this before and I am newbie here.
Thanks,
Click to expand...
Click to collapse
You need "adb"
use following cmd to replace using,
adb shell
su
dd if=/sdcard/backup/pationno.img of=/the/pation/where/you/want/to/restore
beware!
dd is very lethal in wrong hand, I recommend not use until you are knowing what are you doing, we dont have any TWRP so to save your device.
kdm6389 said:
You need "adb"
use following cmd to replace using,
adb shell
su
dd if=/sdcard/backup/pationno.img of=/the/pation/where/you/want/to/restore
beware!
dd is very lethal in wrong hand, I recommend not use until you are knowing what are you doing, we dont have any TWRP so to save your device.
Click to expand...
Click to collapse
I am quite comfortable handling linux command line shells. However, since my Alcatel Streak phone is stuck at boot, not sure how I can get the adb shell?
After several rounds of factory reset, cache reset, no mater what, the phone simply won't boot and it is stuck with "google " or "android" welcome picture.
I noticed a a guideline of using cygwin in windows PC to run dd for backing up the phone partition image. Is it possible that I copy all your dd files into a cygwin in window 10 PC, then use USB cable to move the files into the phone or flash the phone?
jxzz said:
I am quite comfortable handling linux command line shells. However, since my Alcatel Streak phone is stuck at boot, not sure how I can get the adb shell?
After several rounds of factory reset, cache reset, no mater what, the phone simply won't boot and it is stuck with "google " or "android" welcome picture.
I noticed a a guideline of using cygwin in windows PC to run dd for backing up the phone partition image. Is it possible that I copy all your dd files into a cygwin in window 10 PC, then use USB cable to move the files into the phone or flash the phone?
Click to expand...
Click to collapse
nothing will work unless u have /system image, or working ROM.zip,
Since you have corrupted /system, and your model is different then mine is pop445
i did not uploaded /system bc its wqy more size then recovery
kdm6389 said:
nothing will work unless u have /system image, or working ROM.zip,
Since you have corrupted /system, and your model is different then mine is pop445
i did not uploaded /system bc its wqy more size then recovery
Click to expand...
Click to collapse
Thanks for the information. I searched the web and found many stock ROM for download for many Alcatel models except this model.
Alcatel Streak (model 40600) is dedicated for Cricket and it appears that neither Cricket nor Alcatel releases the ROM for this model.
jxzz said:
Thanks for the information. I searched the web and found many stock ROM for download for many Alcatel models except this model.
Alcatel Streak (model 40600) is dedicated for Cricket and it appears that neither Cricket nor Alcatel releases the ROM for this model.
Click to expand...
Click to collapse
share the stock ROM
I have figured out a way to root easier, I have flashed twrp (with some graphical issues... Working on it) flashed Xposed framework on it, and got native tethering working.
This thread is obsolete now,
for rooting read https://forum.xda-developers.com/android/general/super-guide-alcatel-one-touch-4060a-t3621525
Latest Stock ROM we have | https://forum.xda-developers.com/showpost.php?p=74529924&postcount=205
Please Help!
I did something very stupid today.
Unlocked my RMX2170, got into fastboot.
Tried to flash PBRP as recovery, and some vbmeta.img image as vbmeta of my phone.
Disaster! My phone got stuck in a bootloop of just repeatedly booting into fastboot.
No recovery, nothing.
From there, I installed SHRP using the fasboot flash recovery command, and now I have SHRP.
SHRP, however, cannot flash ANYTHING as a result of an error that it "failed to mount /system_root and /vendor"
The phone can effectively boot into Qualcomm EDL and fastboot.
I've tried countless tools and software to get back to stock. Nothing works. MSM requires a login to function, so it won't work.
Anyone at all, please, can you tell me how to get back to FULL stock?
Through sheer trial and error,
Procedure:
1. Downloaded A37 ofp file from www.gsmmafia.com/realme-7-pro-rmx2170-flash-file/ (or mediafire download)
2. Extracted it using bkerler/oppo_decrypt's ofp_qc_extract.py into a folder:
Code:
py -3 -m pip install -r requirements.txt
py -3 ofp_qc_extract.py a37_ofp_file.ofp .\extracted
3. Rebooted the phone into fastboot, ready for flashing (Power + Volume Down for me)
5. Ran:
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
(keep in mind these .img files came from the extracted ofp's folder!)
6. Rebooted into system using the fastboot menu (START)
7. I'm pretty sure my phone ran A41 before today... so I gave the phone an update from inside Android, that seemed to work fine.
As a bonus, my bootloader seems to have remained unlocked? Nice!
Also interesting: holding volume up does not boot into recovery. This is an issue for another day lads.
Can you explain me step 2? I have bootloped phone and I don't understand how to use oppo decrypt
Domac5 said:
Can you explain me step 2? I have bootloped phone and I don't understand how to use oppo decrypt
Click to expand...
Click to collapse
1. Download and install Python on your computer.
2. Press Windows + R, then type cmd, hit enter to access a terminal.
3. Make sure Python works by trying py -3 in the terminal. (Type exit() to exit the Python shell)
4. Download oppo_decrypt's repository zip and extract it in a folder anywhere.
5. Use cd in the terminal to navigate to the extracted folder.
6. Run this command to install the dependencies of oppo_decrypt:
Bash:
py -3 -m pip install -r requirements.txt
7. You should have already downloaded the ofp file for the phone. If not, get it from here.
8. You need to run the Python script in order to extract the images you need, so, you should copy it to the folder where your ofp file is.
Bash:
cp ofp_qc_decrypt.py /where/the/ofp/file/is/ofp_qc_decrypt.py
9. Go into the directory with the script and ofp file, and extract it.
Bash:
py -3 ofp_qc_extract.py the_ofp_file.ofp .\extracted
The extracted images you need, if you were on Android 10, should be in the extracted folder in the terminal's working directory.
Best of luck, although I can't really help you step-by-step for everything, so I suggest you visit r/realme's Discord.
Go to the Discord for more help!
Codian said:
1. Download and install Python on your computer.
2. Press Windows + R, then type cmd, hit enter to access a terminal.
3. Make sure Python works by trying py -3 in the terminal. (Type exit() to exit the Python shell)
4. Download oppo_decrypt's repository zip and extract it in a folder anywhere.
5. Use cd in the terminal to navigate to the extracted folder.
6. Run this command to install the dependencies of oppo_decrypt:
Bash:
py -3 -m pip install -r requirements.txt
7. You should have already downloaded the ofp file for the phone. If not, get it from here.
8. You need to run the Python script in order to extract the images you need, so, you should copy it to the folder where your ofp file is.
Bash:
cp ofp_qc_decrypt.py /where/the/ofp/file/is/ofp_qc_decrypt.py
9. Go into the directory with the script and ofp file, and extract it.
Bash:
py -3 ofp_qc_extract.py the_ofp_file.ofp .\extracted
The extracted images you need, if you were on Android 10, should be in the extracted folder in the terminal's working directory.
Best of luck, although I can't really help you step-by-step for everything, so I suggest you visit r/realme's Discord.
Go to the Discord for more help!
Click to expand...
Click to collapse
Step 8 not working for me
Do you have original recovery.img file,please send me? I just can't extract it from ofp file, 2 days trying and just can't
Domac5 said:
Step 8 not working for me
Click to expand...
Click to collapse
Sorry, instead of "cp" the command is "copy", my mistake.
Domac5 said:
Do you have original recovery.img file,please send me? I just can't extract it from ofp file, 2 days trying and just can't
Click to expand...
Click to collapse
You can't flash recovery.img. It won't work, I tried. You need to re-flash all of the system partitions like in my post.
I don't have the files anymore, as I did this a while ago. Sorry.
Codian said:
Sorry, instead of "cp" the command is "copy", my mistake.
Click to expand...
Click to collapse
Still doesnt work
I did it, problem was in python3 comand, that one should be typed without number 3 because that doesn't work in windows. Now it's extracting
did you had these problem?