I know that this issue has yet to be resolved, but I noticed that it is popping up for some of us P769BK users who decided to be 'guinea pigs' by testing the waters of flashing kdz files from various L9 devices, so I figured it would be best to start an actual thread instead of asking in threads not relevant to the question at hand.
I saw a post by Lelus asking an individual if they could give the touch firmware version, which gave me the idea that this is potentially reversible with some time and patience (mainly for my sake since I have one L9 just to mess around with ). The touch firmware version on my daily P769BK is 6, whereas the firmware version on my "play-around" P769BK is firmware 12 after flashing the India kdz file onto it and flashing it back to stock V10G kdz. Any suggestions on where the touch firmware could be located to be pulled from a working L9 and be pushed onto the other via adb after applying the new rooting method?
Just an info note: both of my P769BK are on V10G, one rooted and OTA updated with Voodoo root keeper, the other one stock V10G with mirrored touch issue.
Sent from my LG-P769 using xda app-developers app
Either v10g kdz doesn't have touch screen firmware update ,or flasher checks version before update and doesn't downgrade I don't think it can be pulled from working phone.
Have you tried flashing your phone with wind 10a http://csmgdl.lgmobile.com/swdata/WDLSW/LGP769/AAWCBK/V11a_00/V11A_00.kdz ?
aequitas3 said:
I know that this issue has yet to be resolved, but I noticed that it is popping up for some of us P769BK users who decided to be 'guinea pigs' by testing the waters of flashing kdz files from various L9 devices, so I figured it would be best to start an actual thread instead of asking in threads not relevant to the question at hand.
I saw a post by Lelus asking an individual if they could give the touch firmware version, which gave me the idea that this is potentially reversible with some time and patience (mainly for my sake since I have one L9 just to mess around with ). The touch firmware version on my daily P769BK is 6, whereas the firmware version on my "play-around" P769BK is firmware 12 after flashing the India kdz file onto it and flashing it back to stock V10G kdz. Any suggestions on where the touch firmware could be located to be pulled from a working L9 and be pushed onto the other via adb after applying the new rooting method?
Just an info note: both of my P769BK are on V10G, one rooted and OTA updated with Voodoo root keeper, the other one stock V10G with mirrored touch issue.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Yes I have tried flashing the Canadian V11A kdz and no luck with that one either. The touch screen is still mirrored, but not entirely sure what the firmware version is, if it stays 12 or changes.
Sent from my LG-P769 using xda app-developers app
When you guys boot is the LG logo mirrored and reverse colored?
---------- Post added at 03:56 PM ---------- Previous post was at 03:50 PM ----------
Maybe if you wipe system with fastboot and then flash kdz?
No LG logo is normal and not inversely colored. Although I didn't think to wiping system with fastboot and then flashing the kdz, I'll give that a try in a little.
Sent from my LG-P769 using xda app-developers app
Lelus said:
Either v10g kdz doesn't have touch screen firmware update ,or flasher checks version before update and doesn't downgrade I don't think it can be pulled from working phone.
Have you tried flashing your phone with wind 10a http://csmgdl.lgmobile.com/swdata/WDLSW/LGP769/AAWCBK/V11a_00/V11A_00.kdz ?
Click to expand...
Click to collapse
Yeah i think u r right about the updater not updating the touch screen firmware...because i get to see several parameters errors reoccurring while flashing any kdz....and if there was any way to reflash the touchscreen firmware then maybe the problem would resolve....i think the TS firmware in the v10E is different (if any user could confirm) then is it possible to downgrade to that firmware...as it seems that flashing the Indian kdz has downgraded the TS firmware....sorry had to get my doubts cleared in front of the experts
I'm pretty sure now that controller module has built-in firmware and it's compiled into kernel. From what I can tell, flashing takes place if the ver present in the EEPROM is at a lower revision than the one embedded into the module.
Tablechair said:
When you guys boot is the LG logo mirrored and reverse colored?
---------- Post added at 03:56 PM ---------- Previous post was at 03:50 PM ----------
Maybe if you wipe system with fastboot and then flash kdz?
Click to expand...
Click to collapse
The LG logo is mirrored and inverse coloured when flashing from Indian kdz to T-mobile v10G....but after flashing the canadian v11A the mirrored effect of the screen goes away...but the touch mess-up issue remains.
---------- Post added at 06:06 AM ---------- Previous post was at 05:54 AM ----------
Lelus said:
I'm pretty sure now that controller module has built-in firmware and it's compiled into kernel. From what I can tell, flashing takes place if the ver present in the EEPROM is at a lower revision than the one embedded into the module.
Click to expand...
Click to collapse
So does that mean flashing a new kernel(namely v10E) or reflashing the same kernel could install the TS drivers afresh?
PROgenitor said:
The LG logo is mirrored and inverse coloured when flashing from Indian kdz to T-mobile v10G....but after flashing the canadian v11A the mirrored effect of the screen goes away...but the touch mess-up issue remains.
---------- Post added at 06:06 AM ---------- Previous post was at 05:54 AM ----------
So does that mean flashing a new kernel(namely v10E) or reflashing the same kernel could install the TS drivers afresh?
Click to expand...
Click to collapse
Unfortunately not... a kernel would have to have touch screen firmware v13 or higher and p769v10g is 6 which is probably latest.
http://forum.xda-developers.com/showpost.php?p=39268215&postcount=24
I'm pretty sure this won't work and can be damaging , but if someone is willing to give it a try:
Unzip 19.bin (which is just 10k of 00's) to sdcard
On a rooted phone with proper stock rom
$ adb shell
$ su
$ echo 1 /sdcard/external_sd/19.bin > /sys/devices/virtual/input/lge_touch/firmware
Reboot phone
Again , there is possibility of damaging your device.
I'll give it a try after testing the wiping of /system via flashboot doesn't do any good lol
Sent from my LG-P769 using xda app-developers app
Anyone give a try? I would but im kinda poor and this is my only phone.
Lelus said:
I'm pretty sure this won't work and can be damaging , but if someone is willing to give it a try:
Unzip 19.bin (which is just 10k of 00's) to sdcard
On a rooted phone with proper stock rom
$ adb shell
$ su
$ echo 1 /sdcard/external_sd/19.bin > /sys/devices/virtual/input/lge_touch/firmware
Reboot phone
Again , there is possibility of damaging your device.
Click to expand...
Click to collapse
I just saw the 19.bin file and as told by you, its 10kilobytes of just Null characters (Hex Code 00).
Are you replacing file with name "firmware" and size only 89bytes with a file of 10000bytes? The file "firmware" actually is a text file which holds only firmware version number. Will this work? Anyone tried?
Doesnt KDZ flashing replaces this file too?
PROgenitor: Have you tried flashing the T-Mobile P769 10G KDZ? If you have not, try this first. Use the instructions posted by cmahendra for gaining root via KDZ flash.
But before doing this, may we have the output from these commands first?
adb shell
su -
lsmod
uname -a
ls -la /sys/devices/omapdss/display0/driver
Here is my output.
Code:
[email protected]:/ # lsmod
lsmod
bcmdhd 410031 0 - Live 0xbf053000
omaplfb_sgx540_120 19252 0 - Live 0xbf04a000
pvrsrvkm_sgx540_120 259245 77 omaplfb_sgx540_120, Live 0xbf000000
[email protected]:/ #
[email protected]:/ # uname -a
uname -a
Linux localhost 3.0.21 #1 SMP PREEMPT Wed Jan 9 16:40:29 KST 2013 armv7l GNU/Lin
ux
[email protected]:/ #
ls -la /sys/devices/omapdss/display0/driver
[email protected]:/sys/devices/omapdss/display0 # ls -la /sys/devices/omapdss/display
0/driver
es/omapdss/display0/driver <
lrwxrwxrwx root root 2013-03-11 00:47 driver -> ../../../bus/om
apdss/drivers/tx11d108vm_panel
[email protected]:/sys/devices/omapdss/display0 #
I am wondering if you have a different kernel, or just a different module. It could still be an init script issue.Would you also be able to share a CWM backup before flashing the KDZ so that I can compare?
kevev said:
PROgenitor: Have you tried flashing the T-Mobile P769 10G KDZ? If you have not, try this first. Use the instructions posted by cmahendra for gaining root via KDZ flash.
But before doing this, may we have the output from these commands first?
adb shell
su -
lsmod
uname -a
ls -la /sys/devices/omapdss/display0/driver
Here is my output.
Code:
[email protected]:/ # lsmod
lsmod
bcmdhd 410031 0 - Live 0xbf053000
omaplfb_sgx540_120 19252 0 - Live 0xbf04a000
pvrsrvkm_sgx540_120 259245 77 omaplfb_sgx540_120, Live 0xbf000000
[email protected]:/ #
[email protected]:/ # uname -a
uname -a
Linux localhost 3.0.21 #1 SMP PREEMPT Wed Jan 9 16:40:29 KST 2013 armv7l GNU/Lin
ux
[email protected]:/ #
ls -la /sys/devices/omapdss/display0/driver
[email protected]:/sys/devices/omapdss/display0 # ls -la /sys/devices/omapdss/display
0/driver
es/omapdss/display0/driver <
lrwxrwxrwx root root 2013-03-11 00:47 driver -> ../../../bus/om
apdss/drivers/tx11d108vm_panel
[email protected]:/sys/devices/omapdss/display0 #
I am wondering if you have a different kernel, or just a different module. It could still be an init script issue.Would you also be able to share a CWM backup before flashing the KDZ so that I can compare?
Click to expand...
Click to collapse
there isn't module for the touch screen, it's statically compiled into kernel
Lelus said:
there isn't module for the touch screen, it's statically compiled into kernel
Click to expand...
Click to collapse
I see.
kevev said:
PROgenitor: Have you tried flashing the T-Mobile P769 10G KDZ? If you have not, try this first. Use the instructions posted by cmahendra for gaining root via KDZ flash.
But before doing this, may we have the output from these commands first?
adb shell
su -
lsmod
uname -a
ls -la /sys/devices/omapdss/display0/driver
I am wondering if you have a different kernel, or just a different module. It could still be an init script issue.Would you also be able to share a CWM backup before flashing the KDZ so that I can compare?
Click to expand...
Click to collapse
I have tried flashing P769 V10G(T-mobile) and V11A Canada(Wind) several times after the issue....but no success...so i flashed the P765 V10C(India) and gained root and installed CWM recovery.....Then via recovery i restored a CWM backup of a rooted P769 V10G(from cmahendra's post)....I am currently on that....i will just try and give you the output.
My Output:
C:\Root\stuff>adb shell
[email protected]:/ $ su -
su -
[email protected]:/ # lsmod
lsmod
bcmdhd 410031 0 - Live 0xbf053000
omaplfb_sgx540_120 19252 0 - Live 0xbf04a000
pvrsrvkm_sgx540_120 259245 67 omaplfb_sgx540_120, Live 0xbf000000
[email protected]:/ # uname -a
uname -a
sh: uname: not found
127|[email protected]:/ # ls -la /sys/devices/omapdss/display0/driver
ls -la /sys/devices/omapdss/display0/driver
lrwxrwxrwx root root 2013-03-12 13:22 driver -> ../../../bus/om
apdss/drivers/tx11d108vm_panel
[email protected]:/ #
Click to expand...
Click to collapse
PROgenitor said:
I have tried flashing P769 V10G(T-mobile) and V11A Canada(Wind) several times after the issue....but no success...so i flashed the P765 V10C(India) and gained root and installed CWM recovery.....Then via recovery i restored a CWM backup of a rooted P769 V10G(from cmahendra's post)....I am currently on that....i will just try and give you the output.
My Output:
Click to expand...
Click to collapse
Does this mean, you have not yet tried LELUS method alongwith direct flashing of P769V10G or P769V11A?
If not yet done, try that with HARDRESET to phone before and after the flashing with Lelus root. :good: Good luck.
Could someone with a phone other then p769 check their touchscreen firmware version.
Lelus said:
Could someone with a phone other then p769 check their touchscreen firmware version.
Click to expand...
Click to collapse
P765 V10G India , Touch Firmware Version: 12.
EDIT:
3845#*765# ---> H/W Device Test --->Touch Test --->Touch Firmware Version : 12
P765: IPS Display
P769: Corning Gorilla Glass
Related
Hi folks,
I am running an unlocked Telus HTC Hero on the Bell HSDPA Mobile Network and I want to root my phone so I can install and use the Market Enabler app (among others).
My "About phone" info is:
Model Number: HTC Hero
Firmware version: 1.5
Kernel version: 2.6.27-0078c992 [email protected] #851
Build number: 2.73.661.46 CL#74632 release-keys
Software version: 1.0.0.A6288
I have read several forum and blog posts and am really confused now as to how to do this...downgrade, upgrade...??
Most posts I have come across seem to refer to older versions of firmware or it may be that I am just a moron--I'm open to that as well
Thanks all!
aus
No takers yet eh?
Can anyone at least point me in the right direction with a few "updated" links? I tried a few methods, but am getting stimied at different points--maybe I need to downgrade my firmware first or something?
Thanks all!
I'm using an unlocked Telus Hero with Rogers right now. I've just been using the stock firmware for a week now. I've been reading a lot of posts about flashing and rooting too, but it seems like doing so will "downgrade" the Telus Hero because the versions in the custom ROMs are lower. But I've read people successfully running Modaco 3.0 on it without problems.
I'm gonna get a bigger microSDHC card this weekend and mess around with it and see how it goes. I think as long as you do a nandroid backup, you can revert back to the stock firmware\settings if something doesn't work.
auslander1138 said:
No takers yet eh?
Can anyone at least point me in the right direction with a few "updated" links? I tried a few methods, but am getting stimied at different points--maybe I need to downgrade my firmware first or something?
Thanks all!
Click to expand...
Click to collapse
I'm not going to hold your hand through the process - there is more than enough information on these forums. I know there is a lot there, but it looks like you have just had a look and went "waaaa too much to read, someone give me the easy way", rather than made a real attempt to understand it.
However, I'm sure many people (myself included) would be happy to help if you are stuck with something and have *specific* questions.
Why not take a good read through the guide and post again with questions about what part of the process you actually don't understand?
I promise you that all the information *is* on the forums, but you have to be willing to help yourself a little bit first
auslander1138 said:
Model Number: HTC Hero
Firmware version: 1.5
Kernel version: 2.6.27-0078c992 [email protected] #851
Build number: 2.73.661.46 CL#74632 release-keys
Software version: 1.0.0.A6288
Click to expand...
Click to collapse
Ok, this is the recepit I used to "root" my brand new unlocked HTC Hero GSM version with build 2.73.x.x.x:
FOR GSM phones only
Code:
Prerequisits:
- Install ADB drives if neccecary (usb_drivers folder)
- Verify installation by connecting phone to PC (USB)
- Enter tools folder
- Type adb-windows shell
- You should get shell access from the phone
- Type exit to quit shell
1. Copy recovery.img to SD card
2. Flash new recovery image
- Install flashrec-1.1.2-20090909.apk
- Copy to SD card and start with a packet installer
- Run application
- First make backup of current recovery image (click backup button)
- Change path in textbox to /sdcard/recovery.img
- Click "flash recovery image" button to flash new recovery image
- If you get "Flash complete" message, reboot phone.
3. Backup current ROM
- Shutdown phone
- Power up phone by holding Home button while clicking Power. Keep holding down Home for a few seconds.
- Use the NANDROID BACKUP menu option to backup current rom
4. Root phone (optional)
- Boot recovery image as above (Home + Power)
- While phone is in recovery mode open cmd.exe on PC and enter tools\ folder
- Type the following commands:
adb-windows shell
mkdir systmp
mount -o rw -t yaffs2 /dev/block/mtdblock3 /systmp
cat /systmp/bin/sh > /systmp/bin/su
chmod 4755 /systmp/bin/su
reboot
- Enjoy rooted phone
5. Install Market Enabler (optional)
- You can now install MarketEnabler_3.0.4.apk to gain access to full Android Market
All I used is included in this zip file: http://www.megaupload.com/?d=TMP4DO01
This worked on my unlocked GSM phone. If you want to try, do so at your own risk.
pananza said:
Ok, this is the recepit I used to "root" my brand new unlocked HTC Hero GSM version with build 2.73.x.x.x:
FOR GSM phones only
All I used is included in this zip file: http://www.megaupload.com/?d=TMP4DO01
This worked on my unlocked GSM phone. If you want to try, do so at your own risk.
Click to expand...
Click to collapse
...awesome tips--thanks for the concise write-up!
I had started down this same path and got off-track with the errors encountered during backup, but this has motivated me to give it another try.
Thanks again!
aus
Need ssome help please guys
After i intall the drivers and Type adb-windows shell..
i get a $
what does this mean,do i need some kind of password?
Administrat0r said:
After i intall the drivers and Type adb-windows shell..
i get a $
what does this mean,do i need some kind of password?
Click to expand...
Click to collapse
I take it you're trying to create a Goldcard? If so once the $ symbol appears type - cat /sys/class/mmc_host/mmc1/mmc1:*/cid
That will give you your CID code which you will need to reverse string.
Administrat0r said:
After i intall the drivers and Type adb-windows shell..
i get a $
what does this mean,do i need some kind of password?
Click to expand...
Click to collapse
The $ is the shell prompt, it shows everything is fine. Just type exit and press enter to get back to cmd.
Hi All,
I have Dell streak with EVT1 hardware. I flash all possible recovery images, but it isn't work. Black screen every time when I launch recovery mode. May be somebody know how to update this hardware?
Phone is working on 1.6 (performance is very poor)
P.S. Sorry for bad English.
Please help!!!
What is the currently installed rom exactly?
NikolayTLM said:
Hi All,
I have Dell streak with EVT1 hardware. I flash all possible recovery images, but it isn't work. Black screen every time when I launch recovery mode. May be somebody know how to update this hardware?
Phone is working on 1.6 (performance is very poor)
P.S. Sorry for bad English.
Click to expand...
Click to collapse
If you have a black screen at recovery with no Dell logo, you probably are going to need to restore your device using the QDLTool3rd.
Typically, this happens when flashing an "update" file mismatched with your recovery. I did this myself recently, and the only way I was able to get back was to use the QDL tool then re-flash my stock ROM.
It literally saved my phone.
EVT=evaluation/testing?
Without knowing the differences in hardware and possibly software you can't assume that solutions that work on production Streaks will work on his phone.
marvin02 said:
EVT=evaluation/testing?
Without knowing the differences in hardware and possibly software you can't assume that solutions that work on production Streaks will work on his phone.
Click to expand...
Click to collapse
EVT=evaluation/testing - Yes
i think that difference between EVT3 (product hardware) and EVT1 - smallest RAM size (145Mb is available)
in on board EVT1:
- QSD8X50 Processor (as per "Android System Info") with 998.4Mhz max frequency.
- Total RAM: 145Mb
I tried flash device via QDLTool3rd - unsuccessful. Maybe i used newest recovery images instead old? Black screen every time when i try to boot it in recovery mode. What additional info about EVT1 is needed and which application can provide this information?
BR. Nikolay.
TheManii said:
What is the currently installed rom exactly?
Click to expand...
Click to collapse
Sorry, but i don't know the currently installed rom.
Info in 'About device' menu:
- Firmware version: 1.6
- Baseband version: GAUSB1A1008151
- Kernel version: 2.6.29-perf
- OEM version: RerforceVerify_1012
- Build number: 1012
You definitely have an enginnering beta streak, from what've seen from attempting to get people to dump their roms off it, trying to update it will prob brick it.
It's only valuable if you can get the rom off it, but otherwise you likely wont be able to use it as a normal streak
TheManii said:
You definitely have an enginnering beta streak, from what've seen from attempting to get people to dump their roms off it, trying to update it will prob brick it.
It's only valuable if you can get the rom off it, but otherwise you likely wont be able to use it as a normal streak
Click to expand...
Click to collapse
Thanks, i think about that. I am use it as normal cell phone right now. But it is not easy, because it will reboot at any time as they wish. I like this phone and it isn't trouble to update RAM (on this device to appropriate size). I just want to know - device is 'upgradeable' to 2.2 or not?
I'l talking with people, which know about this device. And they said me - that this device can be ungraded, but build should be compiled in appropriate kitchen! Maybe somebody have appropriate build rom for this HW type/ or maybe somebody upgrade EVT1 HW?
how much did that specific streak cost you exactly?
You're much better off getting a normal retail streak unless you dont mind the hassle of making everything work on that submodel.
Clearly stock kernels and roms have trouble with that submodel, are you willing to investigate why? and are you willing to be forced to resort to making custom versions of roms just for your specific streak?
I am interested in getting the rom off that, but besides that unless you got it for free/next to nothing it's prob not worth the hassle compared to a retail streak, there's far too few owners of working prototype streaks left for premade roms to work on them
TheManii said:
how much did that specific streak cost you exactly?
You're much better off getting a normal retail streak unless you dont mind the hassle of making everything work on that submodel.
Clearly stock kernels and roms have trouble with that submodel, are you willing to investigate why? and are you willing to be forced to resort to making custom versions of roms just for your specific streak?
I am interested in getting the rom off that, but besides that unless you got it for free/next to nothing it's prob not worth the hassle compared to a retail streak, there's far too few owners of working prototype streaks left for premade roms to work on them
Click to expand...
Click to collapse
Yes, I got them for free. But this is a not major point for me. I would like to understand 'How it works'.... And I request help on this forum. I'm from Russia, Dell Streak mini 5 isn't selling in my country, So I would like to do 'candy' from it (not for sale, for me only). I thinking about purchasing Dell streak mini 5 with broken LCD, to change mainboard between my and broken device. But I'm not sure about compatibility this hardware (and I not have money to buy it........)
P.S. Sorry for bad English again.
I would assume the lcds would be compatable, but this is just an educated guess,
It sounds like a good idea to switch the motherboards if you want a real working streak
as you're not going to be using the original motherboard, could i ask you to make a dump of the system and boot partitions?
we should continue on #dellstreak on irc.freenode if you dont mind, prototype roms and devices are extremely rare and working ones with pre-release roms are even rarer. There's only a handful still in existance now
TheManii said:
I would assume the lcds would be compatable, but this is just an educated guess,
It sounds like a good idea to switch the motherboards if you want a real working streak
as you're not going to be using the original motherboard, could i ask you to make a dump of the system and boot partitions?
we should continue on #dellstreak on irc.freenode if you dont mind, prototype roms and devices are extremely rare and working ones with pre-release roms are even rarer. There's only a handful still in existance now
Click to expand...
Click to collapse
Please write instructions / 'how to' make a dump of the system and boot partitions
Do you know how to use ADB?
you will need to root your phone also before beginning
TheManii said:
Do you know how to use ADB?
you will need to root your phone also before beginning
Click to expand...
Click to collapse
My dell is rooted. I used ADB shell in my practice but a long time ago. So it would be perfect if you provide ADB commands...
Do you still have the original recovery installed?
first do a
Code:
cat /proc/mtd
and figure out which is boot / recovery / system
then do a
Code:
dd if=/dev/mtd/mtdx of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtdy of=/sdcard/boot.img bs=4096
where X and Y are the matching values from the first command
finally do a
Code:
cat /system /sdcard/system
then you'll have boot.img recovery.img (if you still have it) and a folder named system
send those 3 to me
TheManii said:
Do you still have the original recovery installed?
first do a
Code:
cat /proc/mtd
and figure out which is boot / recovery / system
then do a
Code:
dd if=/dev/mtd/mtdx of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtdy of=/sdcard/boot.img bs=4096
where X and Y are the matching values from the first command
finally do a
Code:
cat /system /sdcard/system
then you'll have boot.img recovery.img (if you still have it) and a folder named system
send those 3 to me
Click to expand...
Click to collapse
I used these commands in dell terminal app:
Code:
su
cat /proc/mtd
dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtd2 of=/sdcard/recovery_bak.img bs=4096
dd if=/dev/mtd/mtd0 of=/sdcard/boot.img bs=4096
dd if=/dev/mtd/mtd3 of=/sdcard/system.img bs=4096
After that operations 4 files added to sdcard (recovery.img, recovery_bak.img, boot.img, system.img)
Incorrect length message was displayed after cat /system /sdcard/system command.
All files were added to archive (WinRAR used) and uploaded to fileserver
You have to use
cat /system /sdcard/system
as DD will not work on the system partition
TheManii said:
You have to use
cat /system /sdcard/system
as DD will not work on the system partition
Click to expand...
Click to collapse
following text message is displayed when i try cat /system /sdcard/system command.
Code:
/system: invalid length
/sdcard/system: invalid length
my *nix is really weak,
try
Code:
cp -r /system/* /sdcard/temp
but you might need to manually make /sdcard/temp first or it might get confused
it will complain about symlinks but that's ok
See by the post count, certainly a noob but I think I've done my homework here. I know this is posted in various places with long threads attached but here it is ...
Atrix 4G ATT
I was on 1.8.3 rooted, did the OTA update to 4.5.91. I think I want root back.
Is this thread the safest way to accomplish this?
http://forum.xda-developers.com/showthread.php?t=1138204 (OP)
I'm not concerned with losing any data on the phone as far as media or anything.
abuse away for being new, idiot with android at the moment.
Best and safe way is preinstall method by eval.... Why?
you dont need to unlock your unit it work with lock / unlocked units
So the method referenced in my first post?
1. Flash with RSD (2.3.4 SBF)
Then ...
Hi guys.. here is a useful little /preinstall for you (attached)
Put phone in fastboot mode, then:
Code:
fastboot flash preinstall preinstall.img
fastboot reboot
(older versions maybe need "fastboot -i 0x22b8")
after fastboot & reboot, type in adb ("adb shell") or terminal emulator, exactly:
Code:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
The last step is optional (and next-to-last *should* be unnecessary), as you can install Superuser however you like. In fact, if you've installed it, simply typing "/preinstall/su" is another way to root, and you could then mount /system read-write and copy it into /system/bin.
Many thanks to Brandon & The2d for brainstorming this out in a crazy "there's no way it could be possible" rooting session. There were a lot of harder ways... who knew we'd be so lucky! And thanks to Edgan for the great "dosu" =)
You can find fastboot here: http://forum.xda-developers.com/show....php?t=1138092
Click to expand...
Click to collapse
thanks!
I used this briefmobile method
http://briefmobile.com/motorola-atrix-4g-root
same as you - OTA to 2.3 from stock locked AT&T. Above method worked first time no data loss. YMMV of course.
I specifically did NOT want to use anything related to sbf due to all the warnings about bricking etc. etc.
I'm holding off on BL unlock as right now 2.3 is a great build even with AT&T restrictions/crapware, hoping that the official unlock will drop before stable CM/AOSP builds appear, but you never know lol
I saw this one too but wasn't sure, no issues at all on this one?
EDIT: That was easier than anticipated..... What's next for a noob such as myself? Tech background: UNIX Engineer (AIX/Solaris/Linux) 15+ years *NIX experience. I don't know crap for java, I alright with c, perl, python, korn ....
I can't seem to find any definitive answer any this. I absolutely must have root for a few apps I use daily. So is there any way to root?
Good question. Im on the hunt also. Only need root for a few apps.
spiritcrusher33 said:
Good question. Im on the hunt also. Only need root for a few apps.
Click to expand...
Click to collapse
If there is no exploit the the only way is to unlock the bootloader and flash supsersu from a custom recovery, or run @DooMLoRD's root .imgs
I've not tested either here yet as adb has died on this PC
has anyone successfully loaded 5.0 then unlocked and rooted their phone?
i really want to do this, but if it doesn't work i'm screwed because i absolutely must have root every day with my appradio
First off, unless you have a GPe c6806 then you already have to have an unlocked bootloader to run lollipop at the moment.
Once you have an unlocked bootloader yes you can flash supersu and have root - see AOSP/CM12/GPe/GPe port, all have working root
blueether said:
First off, unless you have a GPe c6806 then you already have to have an unlocked bootloader to run lollipop at the moment.
Once you have an unlocked bootloader yes you can flash supersu and have root - see AOSP/CM12/GPe/GPe port, all have working root
Click to expand...
Click to collapse
of course i have a GPe phone. not complaining, but there is just little info now with 5.0 out about rooting, etc and i'm not sure what i can/can't do to ensure i still have root. maybe unlocking the bootloader for some reason won't work now with 5.0 i have no idea. i just need to make 100% certain that i won't lose root if i jump through the hoops this phone requires with 5.0
knives of ice said:
of course i have a GPe phone. not complaining, but there is just little info now with 5.0 out about rooting, etc and i'm not sure what i can/can't do to ensure i still have root. maybe unlocking the bootloader for some reason won't work now with 5.0 i have no idea. i just need to make 100% certain that i won't lose root if i jump through the hoops this phone requires with 5.0
Click to expand...
Click to collapse
@DooMLoRD posted a rooted system IMG here http://forum.xda-developers.com/xpe.../lollipop-5-0-boot-fotakernel-images-t2960269 but I don't think he ever got around to explaining how to install it.
adfurgerson said:
@DooMLoRD posted a rooted system IMG here http://forum.xda-developers.com/xpe.../lollipop-5-0-boot-fotakernel-images-t2960269 but I don't think he ever got around to explaining how to install it.
Click to expand...
Click to collapse
yeah, that is one of the unfortunate things of the GPe it is like support is needed for two different phones. right now there is very little info out there for 5.0 Gpe unfortunately.
knives of ice said:
yeah, that is one of the unfortunate things of the GPe it is like support is needed for two different phones. right now there is very little info out there for 5.0 Gpe unfortunately.
Click to expand...
Click to collapse
Flash the images in fastboot, just make sure you have updated to 5.0 prior to flashing his rooted /system.
TREMER said:
Flash the images in fastboot, just make sure you have updated to 5.0 prior to flashing his rooted /system.
Click to expand...
Click to collapse
I'll finish writing the guide that I started now adb is working on this PC again...
EDIT
Just tested:
fastboot boot <boot_image_with_recovery.img>
flash supersu (one of the ones for 5/LP)
reboot
Code:
[email protected]:~/dev/AOSP> adb shell
[email protected]:/ $ su
[email protected]:/ # cp system/build.prop system/build.prop.bk
cp: system/build.prop.bk: Read-only file system
1|[email protected]:/ # mount -o remount,rw /system
[email protected]:/ # cp system/build.prop system/build.prop.bk
[email protected]:/ # rm system/build.prop.bk
[email protected]:/ #
Hi I need the combination and firmware for the Samsung Galaxy SM-J337PVPU3ASC1
I flashed it with a combination file.. but now I'm stuck in the factory binary mode so I need to flash it again
with the stock firmware or whatever to get it working again
Was trying to do a google bypass and kinda goofed because I couldn't find the right firmware :/
If anyone could help me out I'd appreciate it!
I did same, on accident though, trying to bypass fpr lock after factory reset...honestly i think this phone is ****, being as nobody seems to know anythang bout it. I called asurian and got free replacement.
SaitoSama said:
Hi I need the combination and firmware for the Samsung Galaxy SM-J337PVPU3ASC1
I flashed it with a combination file.. but now I'm stuck in the factory binary mode so I need to flash it again
with the stock firmware or whatever to get it working again
Was trying to do a google bypass and kinda goofed because I couldn't find the right firmware :/
If anyone could help me out I'd appreciate it!
Click to expand...
Click to collapse
I did the same exact thing, so far I've figured out that with that being the newest flash of combination we upgraded the bootloader to binary 3 now, the only firmware that will work is going to be the PVPU3ASC2 which is April's update but online you have to have membership or pay to download, unless that's all a scam? I just did this same wipe on a j327p and had no problem going up from binary 2 to 3 and flashing stock ROM. But from what I understand there's a way to just turn factory off in the combination ROM. I've spent hours pouring over different avenues to go. I was going to change device id to j337U being the unlocked version but I'm getting stuck on gaining SU permissions in the Shell with this new factory binary ROM. I can get adb shell while it's running and side load from recovery but nothing installs or flashes. I believe it's running a sort I emulated VM instead of running ON the phones persistent memory.
FINALLY someone to talk to about this specific problem. It was my fault flashing the U3 combo instead of the U2arj2 I should've.
Attaining root J337p? Dirtycow?
To gain su permissions after reflashing stock have you tried using the dirtycow exploit. I have found it to be an almost fool proof method to attain temp root and for flashing twrp or cwm. Depending on the phone you may have to modify the source a bit but basically jus go to github and download the dirtycow zip or if your using Linux then use git clone and clone the Repository then extract it rename to whatever you want i use the simple dirtycow. put that and accompanying files on the root of the phone (/sdcard) . now use ADB push to push it to /data/local/tmp. Then ADB shell cd into /data/local/tmp and chmod 777 *. Once thats done depending on your phone its gonna be a little trial and error but use ./dirtycow /system/bin/applypatch /data/local/tmp/(the name of your dirtycow applypatch file). Then the same process with app_process or app_process64 depending on the phone. Reboot. That should take SElinux to permissive. Here is where things get tricky. ./dirtycow /system/bin/run-as /data/local/tmp/(name of your dirty run-as file). If you have the exact dirtycow applypatch file for your phone then proceed to thw next step otherwise do whatever mods you gotta do to get your file right. Now run-as exec ./(dirtycow)-applypatch boot. Once that is finished run-as su and presto you have temporary root to do whatever you feel like. I do the next step manually if youd like to. Download the appropriate twrp for your phone name it something memorable like twrp.img and move it to the /sdcard root of your phone. now su dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery. Reboot to recovery and you should be free to flash a permanent root method like chainfire supersu or magisk. And that is that. But i warn you not all phones store the recovery image there you may need to search around a bit. I use su ls -al /dev/block/bootdevice/by-name or cat /proc. Between those 2 i usually can find where it is. I claim no responsibility for bricked phones. Thank you. I will be doing this to my j337p later today ill let you know what i come up with
Ps. If your phone is relatively new its more than likley it has a property called dm-verity which is enable that is a huge pain and causes encryption to fail while flashing. There are .zip files online i believe called dmverityopt.zip or something to that effect i suggest flashing that before and after any custom rom flash. Or a custom kernel that doesnt have that problem.